MF
Writing
aideveloper-workflowsoftware-engineering

How AI changed the way I build software

Sunday, March 15, 2026 · 3 min read

Something shifted. And it's not going back.

AI coding agents are reshaping how we build software. Not in the way most people think, not the "everyone can code now" narrative, but in a deeper, more structural way that's changing what it means to be a developer.

But let me start from the beginning.

In the last 12 months alone many developers have seen their entire workflow flip upside down. With better LLMs coming out every few months, the bar to build something has dropped to basically zero. Your grandmother, your neighbor, probably someone's golden retriever with the right prompt...anyone can build an app now.

Vibe coding is real and it works.
Or maybe not.

Because shipping real production software is a completely different sport: security, scalability, lifecycle, technical debt and architectural decisions that come back to bite you years later. Stuff no prompt fixes, at least not yet.

The boring plateau

I've been doing this for over 15 years and I'll be honest I was starting to feel a bit bored. The work was solid but nothing felt truly exciting anymore. Same patterns, same problems dressed up differently, same meetings about the same tradeoffs. You get good at something and the cost of that mastery is that very little surprises you.

Then AI showed up and something clicked.

I didn't jump in overnight. First small tasks: generating boilerplate, writing tests, cleaning up repetitive code. Then bigger ones: implementing features from specs, debugging tricky issues, refactoring entire modules. Then I just stopped fighting it entirely.

The turning point

Claude Opus 4.5 and 4.6 were the real inflection point for me personally. Things I used to grind through in days started happening in hours. Onboarding on a new codebase went from painful to almost fun. Almost.

But here's what I didn't expect: the shift wasn't just about speed. It was about what I started spending my time on. Instead of writing every line myself, I was thinking more carefully about architecture, about ticket structure, about how to break a problem down so an agent could execute it well.

The quality of my thinking became the bottleneck, not the quality of my typing.

What actually changed

I started learning faster. When you can prototype an idea in minutes instead of hours, you iterate more. You try the stupid approach just to see why it's stupid. You explore corners of a codebase you'd normally avoid because the cost of poking around dropped to almost nothing.

My taste got sharper. When you're not exhausted from typing, you have energy left to think about whether something should exist, not just how to build it. I started catching bad patterns earlier, pushing back on unnecessary complexity more often and spending more time on the design phase because that's where the leverage actually is.

Collaboration changed too. Code reviews got more interesting. Instead of nitpicking semicolons, the conversation moved to architecture and intent. The code itself became almost a byproduct of a well-structured decision.

What didn't change

The fundamentals haven't moved. You still need to understand systems deeply. You still need to know when an abstraction is hiding complexity versus removing it. You still need experience to smell a bad architectural decision before it spreads.

If anything, these skills matter more now. When execution is cheap, the cost of a bad decision multiplies because it gets implemented instantly and confidently. An agent will build exactly what you ask for, even if what you asked for is wrong.

Where this is going

I don't think AI replaces developers. I think it replaces a version of the job that was already getting stale. The part where you manually typed out the same CRUD endpoint for the hundredth time, the part where you spent three hours chasing a typo in a config file.

What's left is the interesting part: the thinking, the tradeoffs, the architecture. The stuff I got into this career for in the first place.

Something shifted. And honestly, I'm more excited about building software now than I've been in years.

Share