There's a term you hear more and more: vibe coding — building software by directing AI instead of typing every line yourself. Some people sneer at it. I live inside it, and I think it's one of the most interesting shifts in how humans build.
A changing role
Building software used to mean mastering syntax, frameworks, and a mountain of details. That role is shifting. My work now looks more like a project manager crossed with an architect: deciding what gets built, breaking it into clear pieces, giving specific direction, then critically reviewing the results. The AI writes the code; the decisions remain mine.
What people get wrong
Vibe coding does not mean "accept whatever comes out without thinking". Quite the opposite — the quality of the output depends heavily on the quality of the direction. A few things I learned, not always pleasantly:
- Vague direction produces vague products. "Make me a nice website" gets you something generic. The more specific your taste, the more specific the result.
- You still need the basics. Not to write the code, but to notice when things drift off course, and to ask questions in the right language.
- Verification is non-negotiable. Always ask for tests, always check the final result yourself. Trust is good; proof is better.
Why this is a sensible future
Every era has its lever. Farmers got tractors, accountants got spreadsheets, and today's builders have AI. Using the lever isn't cheating — it's the definition of working smart. What changes is the core skill: from typing fast to thinking clearly — knowing what you want, being able to explain it, and daring to decide.
The good news? Clear thinking can be trained by anyone. Including you, the one who feels you "only know the basics". That's exactly where I started.
