Natural Language as Source Code

The future of software development isn’t writing code faster. It’s changing what we consider source code.

Poor Wizard :(. He really should learn to adapt.

For decades, software development has followed a familiar pattern: business professionals figure out what the customer wants, write requirements, and hand them over to developers who translate those requirements into code.

Then QA gets involved, everybody argues about what the requirements really meant, and eventually something makes it into production.

Sound familiar?

What if we eliminated much of that translation?

Imagine a development process where detailed business specifications, written in natural language, are the source code.

Not vague user stories. Not a handful of prompts asking an AI to build something cool. I’m talking about precise, carefully structured specifications that define business behavior, acceptance criteria, and edge cases.

AI takes those specifications, generates tests first, and then writes the application code necessary to make those tests pass.

When the tests pass, the application goes to QA for independent verification.

Get J Steven Perry’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

The benefits? Faster development, less ambiguity, greater traceability between requirements and implementation, and a much more direct role for business-facing IT professionals.

Does this eliminate the need for expert developers? Of course not. Architecture, security, performance, and maintainability still demand expertise. And passing tests doesn’t guarantee a good application, particularly when the requirements themselves are wrong.

But here’s the fundamental shift:

The business specification becomes the version-controlled asset. The generated code becomes an implementation detail. A commodity.

Programming languages will come and go. Frameworks will evolve. AI coding tools will improve.

But a precise description of what a business needs its software to do?

That’s worth preserving.

And increasingly, that’s what we’ll be coding.

What do you think? Leave me a comment and let me know.

Thanks for reading!

— jsp