It does lean into the idea that vibe code is 'Increased productivity, reduced understanding.'
There are too many implicit contextual details that the LLM doesn’t know about that just make coding based on “vibes” not work at all. Eg the size of your organization heavily influences the types of tests you want to write and maintain.
So you still need a very solid understanding of engineering and your domain in order to get it to solve your problems properly.
But in the end, if you learn how to use it well, it’s an insane productivity boost. But you need to spend a month or two to learn how they really work, their limitations, and figure out a workflow.
Anyone that cares to actually do this does not save any time by going with an LLM instead of just coding. For any cases where time saving is actually done, I would argue that the thing coded should either be a framework, a library, or an editor macros (or extensions like JavaBeans generators in Java IDEs).
Quite different from AI-Assist coding.
In other words you're purely playing the PM role rather than the SWE role.
jasonjmcghee•6mo ago
giantg2•6mo ago
mhdhn•6mo ago