dp.cx blog

I've been in this industry long enough to watch careers diverge. Two engineers start at roughly the same place - similar skills, similar experience, similar opportunities. Five years later, one of them is solving problems nobody else can, and the other is doing the same job they started with.

This week I was looking at a Kubernetes deployment and noticed one of the containers was 1.7GB. Nobody asked me to look at container sizes. It wasn't on a sprint board. But 1.7GB is wrong, and I wanted to know why. So I dug in, found the problem, and now there's something concrete to fix. Nothing remarkable about it. But a lot of moments like that add up.

I've watched peers over the years split into two groups. There are people who do what's asked of them, do it well, and clock out. And there are people who read source code they didn't need to read, build things nobody requested, and ask "why" past the point where it's strictly necessary. The first group has perfectly fine careers. The second group ends up driving the direction of the teams and organizations they're part of.

The difference isn't hours worked. It's not "grind more" advice, and it's definitely not "work for free" advice. It's the difference between seeing a 1.7GB container and thinking "that's not my problem" versus "that can't be right." One response costs nothing. The other might take thirty minutes and save your team hours of deploy time, bandwidth, and cost - every single day.

Every time you dig into something unprompted, you learn how a system actually works - not just the surface you interact with for your assigned tasks. To me, that accumulated context is what makes someone senior. Not years on a resume. How well you actually understand what's going on.

People frame passion as this big, dramatic thing. You're supposed to love what you do every day, feel called to your work, whatever. I think that's mostly nonsense. Passion, in practice, looks like not being able to leave a weird log message alone. It looks like reading the docs for a tool you don't use yet because you saw it mentioned in a PR. It's small and unglamorous.

The people I've seen get ahead aren't the ones who followed a roadmap. They're the ones who kept digging.