kinghuang

  Location:            Calgary, Alberta, Canada
  Remote:              Yes
  Willing to relocate: No, but travel OK
  Technologies:        Python, AWS, dbt, spaCy, Dask, Docker, Terraform,
                       PostgreSQL, Redshift, SageMaker, GitLab, and more
  Résumé/CV:           https://www.linkedin.com/in/kinghuang/
  Email:               kinghuang (at) mac (dot) com

My primary project over the past 4+ years involved information extraction from oil & gas invoices using NLP, which allowed me to flex my skills across data science, data engineering, system architecture, and cloud infrastructure. I am highly adaptable and a fast learner!

https://www.linkedin.com/in/kinghuang/

  Location:            Calgary, Alberta, Canada
  Remote:              Yes
  Willing to relocate: No, but willing to travel
  Technologies:        Python, AWS, dbt, spaCy, Dask, Docker, Terraform,
                       PostgreSQL, Redshift, SageMaker, GitLab, and more
  Résumé/CV:           https://www.linkedin.com/in/kinghuang/
  Email:               kinghuang (at) mac (dot) com

My primary project over the past 4+ years involved information extraction from oil & gas invoices using NLP, which allowed me to flex my skills across data science, data engineering, system architecture, and cloud infrastructure. I am highly adaptable and a fast learner!

https://www.linkedin.com/in/kinghuang/

Distance from home to the office is an enormous factor to me. I’m currently an 8 minute bike ride or 25 minute walk from my office, and prefer going in. But, 10 years ago, when it was a 30 minute bike ride or drive, I would’ve loved to WFH.

I feel like all that VC money was actually their undoing. Instead of working with the community, Docker spent bucketloads of money acquiring a lot of community projects and startups in an obvious attempt to become an end-to-end container solution company. But, they didn't have a plan and ended up killing most of those acquisitions. To me, it felt like Docker was using all the money they got to squash the community instead of working with it.

Every year at DockerCon, there would be flashy announcements that went nowhere. As a developer, those years from 2013 to 2017 were both super exciting and super frustrating. Everything started falling apart when Docker (the project) got split into Moby for open source and the rest went commercial. Docker started to sell Docker Swarm (the original), only to kill it a year later with a new Docker Swarm (what we have today). Then, Kubernetes started growing traction, leapfrogging both Docker Swarms, Mesos, and others in adoption. They never had a cohesive commercial plan. Just lots of empty promises and burned bridges.

When I think of Docker (the company), I feel bitter about all the projects they killed in their attempt to own the market. I love using Docker (the software), but the company's just one big disappointment.

This sounds related to the other HN post here: https://news.ycombinator.com/item?id=32996953

In that case, someone pretended to be Connor Tumbleson to get hired.

What great timing! I was just thinking about wanting something to generate a static website for graph data I've gathered in AWS Neptune. I'm definitely going to play around with this when I have some time.

I use and pay for Nova primarily because it's a fully native app, even though it is lacking features compared to Visual Studio Code. Even on the new MacBook Pro with a M1 Pro, simple things like resizing a VSC window is just so much laggier than Nova. I personally value the native implementation of Nova over the features of VSC.

This is false. You can fill in the required information online without a mobile app, and print out the ArriveCAN receipt or write down the 6 character code. There's no need to use a smartphone.

There is the Stream Deck Mobile app. https://www.elgato.com/en/stream-deck-mobile

The AWS integration in the Enterprise Edition sounds interesting. I'm definitely going to try that out.

That's funny. I've had the exact same experience with Bluemix at a Hackathon in the past. It was down for almost the entire weekend, screwing all the teams that didn't pivot early enough.

Interested in using it. I've kept an eye on dotscience and dotmesh for quite some time. At work, we've only very recently ramped up Data Science and ML to a point where tools like these would be really helpful.

I loved all the demos of dotscience I've seen at conferences. I'm saddened that we'll never get to try it, but glad to see that dotmesh will live on!

Oh, man. That's really unforunate.

How will this affect dotmesh?