Forem: Austin King (he/him)

Why is learning Kubernetes so Intimidating?

Austin King (he/him) — Fri, 25 Jun 2021 20:14:37 +0000

During customer interviews, while I was building OpsDrill, I was shocked by something. Very talented DevOps folks were having a hard time learning Kubernetes.

“I’ve been dragging my feet on learning”

“I’ve started and given up 3 times”

“I don’t know where to start, afraid it will mess up my laptop”

“It’s overwhelming”

I was relieved to hear this as I also found it intimidating.

There is a lot of great free tutorials out there, but some of it feels like jumping straight into “Kubernetes 301: PhD in Containerology”.

(Kubernetes the Hard Way I’m looking at you. An amazing resource, but a very steep on-ramp for busy DevOps folks.)

In the past I’ve built games for learning as well as spaced repetition apps for helping to memorize materials. Would you be interested in

An adventure game
Played 15 minutes a day
Using real Kubernetes commands
To really, finally, learn Kubernetes?

Pirates of the Kubernetes waitlist for early access

Join at https://piratesofthekubernetes.com

Know React, but you've fallen behind?

Austin King (he/him) — Fri, 18 Jun 2021 18:16:28 +0000

Do you know React, but you've fallen behind on recent updates? I'm looking for 5 React devs who want free 15 min 1:1 Zoom coaching sessions, so I can test out some micro-course content.

DM https://twitter.com/ozten/ or reply below to sign up.

Please "Heart" this post to spread #reactjs

4 types of engineers

Austin King (he/him) — Thu, 04 Mar 2021 18:27:15 +0000

There are 4 types of engineers: Starters, Maintainers, Optimizers, and Operators. I've found this to be a super helpful model for understanding different my work life. Which is your dominant trait?

The Starter loves to start new projects. They can rapidly build an MVP. They are great with ambiguity and design. They are customer obsessed.

The Maintainer is reliable, loves structure, and is a work horse. Every day they are carving the stones that build the multi-generational cathedral that will last for centuries.

The Optimizer loves puzzles, algorithms, and are often competitive. They know how to load test the software, profile the code, and get satisfaction out of shipping highly performant code.

The Operator loves to learn the ins and outs of an existing system. They know how to deploy it. They love operational readiness. They are experts on the infrastructure. They gleefully find bugs and know everything about the software.

If you put a Maintainer on a greenfield project to build a prototype, they will be miserable. The Starter thrives on a blank canvas and evaluating cutting edge technologies. The maintainer will be frustrated with the lack of focus and craves incremental progress as a SME.

What do you think of this idea?