The Best Years of Our Industry

Go back three years and getting money out of a developer was like drawing blood from a stone. Five dollars a month for a better tool? Forget it. We'd rather spend a weekend configuring Vim, chain together free CLIs with shell scripts, and duct-tape workflows out of spite than hand over a credit card. The entire developer tools market was built on the grim reality that engineers would endure almost any amount of pain before they'd pay to make it stop.

Now those same developers are spending north of two hundred dollars a month on AI coding agents without blinking.

That's not an AI story. That's a developer story. And I think it reveals something about this profession that we've been circling for decades without ever quite naming.

We Were Never in It for the Code

Every productivity tool that came before was selling us the same pitch: be better at implementation. Faster at boilerplate. Fewer bugs. Tighter feedback loops. And we shrugged, because none of it touched the thing we actually cared about. It was like selling a better shovel to someone who resented digging holes.

Here's what the tool vendors missed: most of us didn't get into this for the code. The code was a means to an end. We're builders. We always were. Some of us picked up a keyboard because it gave us a world we could control. Others because it was the fastest way to get an idea out of our heads and into someone else's hands. Others still because it was an escape — a place where the rules were logical even when the rest of life wasn't.

The code was never the point. The building was.

The Journey That Shapes You

That said — and this is the tension at the heart of it — the journey matters. Writing software changes how your brain works. You start seeing systems everywhere. You develop an instinct for where complexity hides and a deep, almost physical aversion to unnecessary complexity. You learn to hold contradictions in your head, to think in abstractions and edge cases simultaneously, to plan for failure as a first-class concern.

That process is formative. It rewires how you approach problems, how you navigate ambiguity, how you work inside complexity and — perhaps more importantly — how you learn to avoid it. (Every senior developer's greatest skill isn't what they can build. It's what they convince everyone not to build.)

The people who stay in this industry long enough all seem to converge on a similar maturity. The syntax wars fade. The framework churn becomes background noise. What remains is simpler and harder to articulate: we love building systems. We love creating things people use. We want to stay in the game long enough to get genuinely good at it, and we want to help others do the same without burning out along the way.

What We Were Actually Willing to Pay For

So when AI agents showed up, they weren't selling us efficiency. They were selling us back the part of the job we fell in love with.

A better linter saves minutes. An AI agent saves days. But the real currency isn't time — it's the kind of work that fills those hours. The two hundred dollars a month isn't buying faster implementation. It's buying the ability to operate at the level we always wished we could. Architecture instead of semicolons. Intent instead of syntax. The interesting problems instead of the tedious ones.

The money was always there. It just needed to buy the right thing. Not productivity. Not efficiency. The joy of building without the tax of drudgery.

Freedom to Enjoy This Again

So much of this career has been spent in the trenches. Fighting scope. Fighting time. Fighting cost. Shipping things you're not proud of because the deadline didn't care about your standards. Watching good engineers burn out and leave because the ratio of meaningful work to soul-crushing work finally tipped the wrong way.

AI hasn't just changed what we can build. It's changed how it feels to build. For a lot of developers, it's brought the fun back. That feeling from your first side project — when you were just making something because you wanted to, before anyone told you to write tests or estimate story points or justify your technical decisions to someone who doesn't understand them. That feeling.

A small price to pay to feel the joy that brought us here in the first place.

Buying the Best Years

Here's the part I keep coming back to: this practice might one day die out. Not tomorrow, not next year, but the arc is visible if you're honest about it. The craft of writing software by hand, the way we know it, may eventually become as niche as hand-setting type or developing film.

And if that's true — if we're somewhere near the peak of a practice that won't last forever — then what we're really buying with those subscriptions is something more poignant than productivity.

We're buying the best years of our industry.

The years where human judgment still matters. Where architectural taste and hard-won intuition are amplified rather than replaced. Where the tools are powerful enough to remove the drudgery but not yet powerful enough to remove us.

I couldn't think of a better time to be a developer. Not because AI makes it easy, but because for the first time, the tools are letting us do the work we actually came here to do.

The building. It was always the building.