I don't think you understand why context-free languages are used for programming. If you provide a requirement with any degree of ambiguity the outcome will be non-deterministic. Do you want software that works or kind of works?

If someone doesn't understand, even conceptually how requirements

The thing that's assumed in "proompting" as the new way of writing code is how much extrapolation are you going to allow the LLM to perform on your behalf. If you describe your requirements in a context-free language you'll have written the code yourself. If you describe the requirements with ambiguity you'll leave enough of narrowing it down to actual code to the LLM.

Have it your way, but the current workflow of proompting/context engineering requires plenty of hand holding with test coverage and a whole lot of token burn to allow agentic loops to pass tests.

If you claim to be a vibe coder proompter with no understanding of how anything works under the hood and claim to build things using English as a programming language, I'd like to see your to-do app.

Yes, but knowing how to read and write syntax is a required pre-requisite.

Syntax, even before LLMs, is just an implementation detail. It's for computers to understand. Semantics is what humans care about.

I have a hard time believing any of these natural language only prompters are being hired as developers if they don't understand the syntax. Part of the issue is LLMs are indeterministic and hallucinate. They also don't recognize every bug they generate.