We Can't Name Variables. Now We're Writing Prompts? (davidadamojr.com)

We used to rely on compilers for clarity.

Now we rely on language models that don't throw errors when we're imprecise. Programming is becoming less about logic and more about articulation in natural language.

Somewhere, an English teacher is smiling, smugly.

So far, I have found that good AI-generated code comes from good developers. The prompt flow that seems to work best is to be able to break down a problem in logical steps, articulating specific requirements along the way. Sometimes it makes sense, and you develop intuition for, when to ask the AI to just stub out service to come back to later. In other words, good prompting for software developer appears to require some of the core problem-solving skills needed to be a good developer in the first place.

As an aside, I also sometimes ask AI agents to help me rename variables!

The variable naming problem never went away. We just moved it from "temp2" to "make this better."

Same skillset. Different enforcement. Compiler used to force clarity through syntax errors. AI forces it through three debugging cycles when you realize the output doesn't match what you thought you said.

Natural language was never designed for precision. We spent decades building tools that forced precision. Now we're back to ambiguity at scale, and the engineers who couldn't name variables are writing paragraph-long specifications.

Logic is abundant. Clarity is the new bottleneck.