From Syntax to Intent
For decades, learning to program meant first learning a language — a strict, unforgiving notation where a misplaced colon crashes your whole program. Python has its indentation rules. JavaScript has its semicolons and curly braces. C++ has things that can make grown engineers cry. The language had to be learned before you could build anything. Something fundamental is shifting. The hardest part of programming is no longer typing the correct symbols in the correct order. It is knowing what you want clearly enough to express it well. That is the move from syntax to intent.
What Syntax Is, and Why It Was the Bottleneck
Syntax is the grammar of a programming language — the exact rules for how instructions must be written so the computer can understand them. Every programming language has its own syntax, and computers enforce it absolutely. Write 'pint' instead of 'print' in Python and nothing works. Forget a closing parenthesis in JavaScript and the whole script breaks. For most of computing history, this was the first wall beginners hit. You wanted to build something creative and useful, but you spent the first weeks fighting punctuation. The ideas were in your head; the syntax was in the way. Modern AI coding assistants can handle syntax perfectly. They have been trained on hundreds of millions of lines of code across dozens of languages. They do not make typos. They know every rule. Syntax is now something the AI handles on your behalf — which frees you to focus on the thing that was always more important: knowing what you want to build.
Traditional coding: learn syntax first, then express ideas through it. Vibe coding: express your idea first, in natural language, and let AI handle the syntax. The skill that now matters most is the ability to describe your intent precisely and clearly.
Think about the difference between these two instructions to an AI: Weak: 'Make a button.' Strong: 'Add a blue Submit button at the bottom of the form. When the user clicks it, check that all required fields are filled in. If any field is empty, show a red error message next to it. If all fields are filled, show a green confirmation message that says Your response was saved.' Both are natural language. Only one communicates intent clearly enough for an AI to produce exactly what you want. The second version required no knowledge of HTML, CSS, or JavaScript — but it required careful, precise thinking about what should happen.
Intent Has Always Been the Real Work
Here is something experienced programmers know that beginners do not: writing code was never the hard part. The hard part was always figuring out exactly what the code should do — edge cases, error conditions, what happens when a user does something unexpected. A professional developer might spend 30 minutes writing 50 lines of code and 4 hours deciding what those 50 lines should do. The thinking, the planning, the questioning — that is the work. Syntax was just transcription. Vibe coding does not eliminate the hard part. It eliminates the transcription. You still have to do the thinking. In fact, you have to do it more explicitly, because now your thinking is the direct input to the system. Sloppy thinking produces sloppy software, with or without AI.
Flashcards — click each card to reveal the answer
If you tell an AI 'make it look better,' you will get something — but probably not what you had in mind. The AI cannot read your mind. It can only work with what you give it. Imprecise input guarantees imprecise output.
Which of these best describes 'intent' in the context of vibe coding?
Why does imprecise natural language produce poor code from an AI?
Precision Upgrade
- Step 1: Read this weak prompt: 'Make the app look nicer and work better.'
- Step 2: List every question an AI might have to answer just to attempt that request. Write at least five questions (e.g., 'Nicer how — color, font, spacing, layout?').
- Step 3: Now rewrite the prompt as a precise description of two specific improvements. Name exactly what you want changed and what the result should look like.
- Step 4: Compare your rewrite to your original. How much more information did you have to provide?
- The gap you just measured is the new core skill.