The Engineer Who Vibe Codes
Working with AI every day changed how I think about what makes someone a "real" developer. I used to believe that meant writing everything from scratch, understanding every layer, never leaning on a tool to fill the gap. Watching how people actually build now, I don't believe that anymore. But I don't believe the opposite either.
Right now there are two obvious kinds of builder.
Engineers
They know why something works, not just that it does. They debug from first principles instead of guessing. They design for scale before it's needed, because they've seen what happens when nobody did.
Vibe coders
They know how to ship. Prompt, iterate, launch, repeat. They move fast, learn by doing, and get a working product in front of people while an engineer is still writing the data model.
Vibe coders are winning the short game. More shipped, more experiments, faster feedback loops. But speed without understanding has a ceiling, and the ceiling shows up as codebases nobody can maintain, bugs with no discoverable cause, and systems that fall over under real load — not the load in the demo.
AI didn't lower the bar here. It changed what the bar actually measures. Execution is table stakes now. Understanding is the differentiator.
The third type
There's a builder who doesn't fit either category cleanly: the engineer who vibe codes.
They understand the system deeply, and they use AI to move through it faster — not instead of thinking, but because they already know what they're asking for. They review generated output critically, because they know what "wrong" looks like before they even run it. They ship at vibe-coder speed with engineer-level judgment.
That combination is rarer than either extreme, and it's the one actually compounding right now. Not because it's a nicer story, but because it's the only version where speed doesn't eventually cost you the thing it was supposed to save.
If you're learning to build right now, the useful move isn't picking a side. It's not stopping at "it works." Ask why it works. Break it on purpose and see what happens. Learn what the AI is actually doing underneath the prompt, even in the sessions where you let it do most of the typing.
The rarest person in the room isn't the fastest builder or the deepest thinker. It's the one who's both.