Every few years the tools change and everybody either panics or throws a party, depending on what they’re selling. This round is different — but not for the reason the AI companies want you to believe.
I’ve been building software since before “the cloud” was a phrase people said with a straight face. For most of that time, the thing clients paid me for was writing the code. That was the bottleneck. That was the skill. That was the invoice.
That part just got cheap. And honestly, I think that’s great — as long as you understand what it actually means.
Writing code was never the hard part
Here’s the uncomfortable truth for a lot of my profession: generating code was the easy part of running software in a real business. It always was. It just didn’t feel that way, because it took so long.
AI closed that gap. A capable person with the right tools now ships in an afternoon what used to eat a week. I use these tools every day and I’m not going back. But if the only thing you take away is “software is cheap now,” you’re going to hurt yourself.
The hard part didn’t disappear. It moved.
Say a shop wants to stop writing quotes by hand. The AI writes the quoting logic before lunch. Feels like magic. Then the actual job starts:
- Pulling live pricing from the system that really holds it — not a copy that’s three weeks stale.
- Making sure the thing can’t fire a wrong number off to a real customer.
- Logging every quote, so when somebody asks why the price came out the way it did, you can actually answer.
- Catching the case where the part’s been discontinued and nobody updated the sheet.
- Deciding who gets a text at six in the morning when it does something strange — because eventually, it will.
None of that is “writing code.” That’s engineering. It’s the wiring, the guardrails, the dashboards, the backups, the rollback plan — the boring stuff that decides whether your slick new tool is an asset or a liability.
Anybody can build the demo. Keeping it alive inside a business with real money moving through it is a different trade entirely.
And then there’s security, which never sleeps
Give a piece of software the ability to actually do things — send email, move money, change records — and you’ve built a new door into your business. The people trying to walk through that door get better every week, and they don’t take weekends off.
Security isn’t a checkbox you tick at launch. It’s something somebody has to keep owning, on purpose, forever.
So what are you actually hiring for now?
Not a coder. Coding is table stakes — the tools handle a big chunk of it.
You’re hiring for judgment. Somebody who knows the options you can’t see. Who’ll wire your existing systems together instead of ripping them out and starting over. Who builds the alerts and the off switch before anything goes live. Who’s still around when it breaks — and it will break. And ideally, somebody who’ll teach your people to run it instead of keeping you on the hook forever.
That’s the job now. Less “developer,” more “the person who keeps the whole machine running.”
We didn’t just decide this — we live it
We run our own company on agents. Client routing, billing, the boring back-office grind — a small team doing the work of a big one, because we engineered it that way.
So when I tell you an agentic system can run a real business, I’m not reading it off a slide. I’m describing my Tuesday.
If there’s a slow, expensive, error-prone corner of your business and you’re not sure whether the answer is a tool, a system, or just a conversation — that’s the exact thing I like to figure out. No pitch. Just a straight answer about what it’d take.