This omits the deep knowledge required for traditional coding. This opens up coding to non devs, e.g. product managers.
For vibe coding you need systems thinking, planning and logic, but less craftmansship.
For PO's the chart looks different, here the traditional flow contains: "polish concepts, make mocks, make stories, dailies, handovers, revisions, waiting for devs busy with other things"
The vibing PO has none of that.
Not saying this is sustainable for big projects already, but it is for ever growing "small" projects (especially if it's a techincal PM that can code a bit). It's just so much faster without devs -_-.
Disclaimer: I am such a PO. What I now wonder: how can I mix vibe coding and properly developed foundations (ai assisted, but not 99% vibed). One answer in my view is splitting services in vibecoded and core, but dependencies on the core already slow you down a lot. Curious to hear how others mix and match both.
What I actually do right now:
- fullstack PoC vibecoded
- specifications for core based on PoC findings
- Build proper vibecoded V1 mocking what moves to core. But here already a more structured vibecoding approach too.
- replace mocks with actual core
Not yet done but planned: build throwaway PoC in a branch of the core so I can also vibe on top of the core directly, including modification of the core.