Blog

This is the first post in a series for new operations and cloud engineers getting started with Kubernetes. Whether you’re running K3s on a Raspberry Pi, EKS in AWS, AKS in Azure, or anything in between, the concepts are the same. Let’s get into it.

You’ve got a Kubernetes cluster. You’ve got an ingress controller routing traffic. You hit your app over HTTPS and… you get a browser warning about an untrusted self-signed certificate. Or worse, you’ve got ten services and you’re copy-pasting the same TLS secret into every single Ingress resource.

The fix: set a default TLS …

During my regularly scheduled lurking on Hacker News, I came across Don’t Become an Engineering Manager, making the case that senior engineers should stay IC. The ladder is flattening, Staff pays better, tech is moving too fast to step away. Probably right, but it bugs me.

It treats the EM role like a career trade. A thing you optimize for or against. And when you look at it that way, sure, the math is shaky right now. But that skips the question I actually care about: what does a good engineering manager do for the engineers on their team?

The best EMs I’ve worked with spend most of their time on the …

Every bug I’ve ever shipped happened because the system did exactly what I told it to, not what I meant. That gap, between what I intended and what I actually built, is where most of the interesting lessons live.

Last week, on three separate occasions, sharp engineers held back their ideas in meetings because they were afraid of being wrong. I only heard those ideas afterward, in side conversations. Every single one of them would have moved the discussion forward, regardless of whether they turned out to be “right.”

That stuck with me.

Here’s the thing: most developers don’t blog. I haven’t in a long time. And that’s a shame, because it’s one of the easiest ways to level up your skills, stand out, and open doors you didn’t even know were there.

I’m not talking about some corporate PR thing or a perfectly polished tech journal. I mean your own little corner of the internet where you write about what you’ve learned, what’s broken, and how you fixed it.

The moment you try to write about a tricky bug or a new library, you realize all the gaps in your own understanding. Filling those gaps? That’s where the real learning happens.