expectedwrong hindsight

We Are Six Months Away

The step change is already here — the org chart just hasn't noticed yet.

2 min read 380 words #ai #agentic-ai #engineering #software-development #automation
hindsight — nailed it

We're basically there. Claude Code, Cursor, Windsurf — employees are building bespoke business functions without filing tickets. The three-week wait for a header change looks even more absurd from this side.

Any employee with internet access and a LinkedIn profile will be able to connect a CRM record to a live enrichment pipeline, run qualification logic against it, and cross-reference the whole thing against internal databases — as a bespoke, one-off business function — without filing a ticket, without a sprint, without anyone's help. Six months away. Maybe less.

Right now that same employee is waiting three weeks for an API endpoint header change.

There's a specific kind of cognitive dissonance you get when you can see both of those realities at the same time. The header change isn't going away next quarter. It's just that next to what's coming, it looks like what it is — a rounding error dressed up as a dependency.

The thing I keep turning over is the recursion of it. Agentic AI building applications. Those applications using agentic AI. And then you, the human, sitting somewhere above it, orchestrating — not writing, not reviewing line by line, but setting intentions and watching things get built. Rapid deployment of applications for which you have zero concern for the code whatsoever. Some you glance at. Some you have to control — auth, customer data, the stuff where "trust me" isn't a risk posture — but even those, you let the AI build and you verify the surface.

The deployment concern and the code concern decouple completely. That's the actual step change. Not "AI writes faster code." It's that code stops being the thing you carry around in your head.

I never thought I would live in a world where I could just ask nicely to affect how a function returns.

That sentence sounds like nothing until you sit with it. Asking nicely. To affect how a function returns. We spent decades learning to speak the machine's language. Now it's learning ours, and it turns out ours is fine. Our language works. You can just say what you want and something goes and does it.

The companies that get there first aren't going to have better engineers. They're going to have better orchestrators — people who understand what to ask for, how to verify what came back, and where to keep a hand on the wheel. The engineering concern doesn't disappear. It stratifies.

We gotta be building there.