I keep coming back to this thought: what if the real source of truth in software isn’t the code anymore? For decades, we’ve treated code as sacred. You write it, you read it, you debug it, and that’s how the world works. But I don’t think that’s going to hold much longer.

The tools are different now. AI is finally good enough to take a clean, structured specification and turn it into code across languages and frameworks. Not perfect, not magic, but solid enough to get the job done. And when that happens, something shifts. Suddenly, the thing you really trust isn’t the code—it’s the spec.

That changes the whole vibe of development. In the past, we obsessed over language wars, frameworks, syntax details. All those hours spent debating curly braces or semicolons. But if the AI can spit out code in whatever stack makes sense, then the language starts to matter a lot less. The only real question becomes: did the program deliver the business need? That’s it.

This reminds me of the jump from assembly to higher-level languages. Back then, developers stopped worrying about machine instructions. Now, we might stop worrying about Python vs. Java vs. TypeScript. Specs are the new code. Write it well, and the AI picks the stack for you.

Of course, that opens up a new set of problems. What does a “good spec” even look like? How much detail is enough, and when does it get too heavy? Specs need to be clear enough for both humans and machines. That’s not easy. And it also changes the developer role. Less grinding through syntax, more thinking like an architect or product designer. At the same time, it makes building software more accessible. If you can describe what you want clearly, you can build.

I don’t think we’ve fully grasped how big this shift could be. It’s not just a productivity boost—it’s a different way of working. The bottleneck moves from typing code to defining problems. And maybe that’s the real superpower: being able to write specs that are sharp, human-friendly, and machine-friendly all at once.

What excites me most is how wide this opens the door. More people can create, experiment, and solve problems without caring about curly braces. We’ll figure out the messy parts as we go, but the direction feels clear: specs first, code second.