Why Specifications, Not Code, Are the Future of Software Engineering?

I just watched Sean Grove’s talk, "The New Code", and it perfectly crystallizes something I’ve been thinking about: The true value of a software engineer is not in writing code, but in writing clear, robust specifications.

“In an era where AI transforms software development, the most valuable skill isn't writing code—it's communicating intent with precision. Specifications, not prompts or code, are becoming the fundamental unit of programming, and spec-writing is the new superpower.” — Sean Grove, OpenAI

As AI systems become more capable, the bottleneck in building great software isn’t implementation—it’s clarity of intent. AI can write code, often better and faster than humans, if you give it a good spec. So the differentiator for us is: Can we shape, validate, and evolve intent clearly?

Sean nails it:

“Code is sort of 10 to 20% of the value that you bring. The other 80 to 90% is in structured communication... talking, understanding, distilling, ideating, planning, sharing, translating, testing, verifying—these all sound like structured communication to me. And structured communication is the bottleneck.”

This is why I believe:

• The clarity of your spec—and how you validate it with evals or tests—is everything.
• You can always generate code from a spec, but not the other way around.
• Updating code without an initial spec is unsustainable—especially as systems evolve faster than ever.

Sean’s analogy is spot-on:

“A written specification is what enables you to align humans on the shared set of goals... This is the artifact that you discuss, debate, refer to, and synchronize on.”

And just like the US Constitution is a versioned, living document with tests (judicial review), our specs should be the primary source of truth—versioned, executable, and always evolving.

With specs as the source of truth, we can safely change and iterate multiple times a day. But tests and evals are the heartbeat of this process.

“Whoever masters writing specifications that fully capture intent and values becomes the most valuable programmer.”

This is the future:

• Specs as code
• Tests as validation
• AI as the implementer

Let’s get really, really good at writing specs.