# vibe coding
← All tags · 5 post(s)
Wall Street Is Dumping Software Stocks, Because Products Can Now Be Conjured in One Sentence
Jefferies just cut Workday, DocuSign, Monday.com, and Freshworks to Hold, citing AI disruption risk in plain language. Software stocks are down 30% to 55% this year. The market is making one bet: once a product's features can be cloned by AI in a single sentence, the business of charging subscriptions for those features stops being worth anything. The point isn't that software dies. It's that the valuable part of software is moving — out of the features themselves and into judgment, taste, distribution, and trust. Anyone who misses the move falls with the multiples.
Even With AI, You'll Still Ship Garbage
Lovable is celebrating 50 million projects and 720 million monthly visits — do the division, and the average project gets seen 14 times a month. AI didn't kill garbage products. It maxed out garbage production capacity. Garbage was never about failing to build it. It's about something that never should've been built in the first place.
vibe coding Is Dead — Write Specs Instead? PMs Have a Third Option: Speak It, AI Builds It
Everyone's shouting that vibe coding is dead and the answer is spec-driven development. But for product managers, front-loading a pile of detailed spec documents just drags back the PRD burden AI finally got rid of. You don't have to choose between 'winging it' and 'writing specs' — there's a third path: speak it, AI builds it.
"AI code is garbage"? Critics are half right — the missing word is *phase*
Mid-2026, vibe coding has split the room in two: one camp calls it the biggest shift since cloud, the other calls it gift-wrapping AI slop. The critics' concerns about security and maintainability are valid — for production systems. For prototypes, they're wildly overstated. doaipm's high-fidelity + safety-net approach has always kept those two things separate.
Vibe coding is already obsolete — and that's great news for product managers
When AI writes the code, what's left is judgment: deciding what to build, for whom, and what 'good' means. That has always been product management. Here's why not knowing how to code can be an advantage — and how to do it on purpose.