4 ms·
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 thinki
by anotheryou 1y ago
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.
- kjkjadksj 1y agoThe deep knowledge really isn’t all that deep. A couple years in the weeds and you have it. What this really hurts is outsourced devs. In the past a non coding person could come up with the spec and hire someone from a developing nation to make it on the cheap to that spec. It is still possible to work like this of course, resulting in working code compared to llm that might hallucinate a passing test condition that you can’t appreciate with your lack of coding chops. It is just the ai seems “faster” and the way it is paid for less in front of your face. Really in practice, nothing new was really gained. Pm always could hire code. Now they hire nondeterministic generated code but they are still essentially hiring code, submitting spec, having something else write the code.
- anotheryou 1y agoBut the feedback cycle wait time and the communication workload is almost eliminated.
- kjkjadksj 1y agoPerhaps. Then again, most people aren't working in fields where racing to the finish is a requirement. Corporate work I've found is really slow moving for a lot of reasons. Things getting backburnered and pushed back is pretty standard. It takes time for all the stakeholders to digest information and make feedback. There is also the phenomenon where no one really appreciably works after thanksgiving so for most american corporate workers it is like they are on a 10.5 month year as it is. All this to say that even with diminished feedback cycle wait time and lightened communication workload, I don't think the product is getting out any faster.
- yeasku 1y agoI must have very low IQ because I have been codding for 25 years and I learn new thing every day. Or you are just writing the same React components every day.