Keep Building Without Getting Paid

The best developers don’t stop building when they close the laptop. In an age of agents, your hobby might be the most irreplaceable thing about you.

Have you ever heard of Pan de Jamón? I hadn’t—until I met Mike, one of the best developers I ever worked with.

This isn’t a “here’s what bread taught me about life” post. It’s an observation that might bring some light to an AI outlook that can feel pretty dark sometimes.

What made Mike stand out wasn’t only his personality or skillset. It was that he went home and baked Venezuelan Christmas bread.

Ode to the Hobbyist

And it wasn’t only Mike. Most developers I remember, I remember by their hobby.

Just off the top of my mind:

• The genius printing parts on a 3D printer he built himself
• The audiophile building a sound system for a perfect pitch
• The home-automation engineer who wired his house with PLCs
• The architect drilling a water well in his own backyard
• The rotary-engine-obsessed designer with a Mazda RX-7
• The 3D specialist restoring a surf van with his son

None of this is on their LinkedIn profile. None of it pays. And it’s the most interesting thing about them.

I’ve spent a long time in enterprise software, working with developers who write code that runs critical infrastructure.

The pattern is so consistent it stopped being a pattern and started looking like a characteristic: The best developers I’ve worked with don’t stop building when they close the laptop. They go home and make something else—bread, sound, water, vans. They just stop getting paid for it.

What Agents Don’t Have

We live in interesting times. Agents are now colleagues that cooperate in writing our code. And companies are considering, or actively pursuing, what that means for headcount. More and more developers are asking: “Will there be a job for me? How do I compete?”

But here’s what agents don’t do. They don’t drive home and pick up a task that’s not on a kanban board. They don’t lose a Saturday to a bad weld or experiment with different kinds of dough and oven temperatures. They don’t bake a loaf that fails three weekends in a row and quietly absorb the lesson that some processes can’t be hurried, no matter how clever the idea. They don’t ferment, restore, dig, solder, role-play or rebuild.

Agents have no Saturday. They have no irrational, over-obsessed curiosity we call a hobby.

Hobbies are unpressured, unstructured, unscheduled—messy mindbenders. That’s what agents miss. And this unpaid labor is where a lot of real learning happens. The kind that doesn’t show up in the sprint demo, but shows up in great architecture decisions, clever unit tests and surprising solutions.

Don’t Give Up on Your Hobbies

If you’re a developer wondering what to do with the noise about AI replacing you, here’s an honest answer: Look beyond the code. Lean harder into the things you make that nobody pays you for.

Your hobby isn’t a side-quest to the main game of being a developer. It’s not only about balance, self-care or free time. It’s where you keep growing the part of yourself that an agent can’t copy. Where character is formed. Where unconstrained thinking is allowed and you explore solutions only you have to justify.

That wonderful waste of a Saturday is the perspective that breaks through on a mundane Monday morning.

The coffee chat “what did you do over the weekend?” might be the context that wins over the agent whose most coffee-related moment is running a brew command in the terminal.

So bake the bread. Dig the well. Restore the van. Roll the dice.

Keep building without getting paid. That’s the work that keeps you irreplaceable.