The 70% problem: hard truths about AI-assisted coding
The definitive essay on why the last 30% still needs engineering.
Open addyo.substack.com →
Building & Product
Article
Article
Article
Article
Article
Article
Article
Article
Article
Article
Article
Article
Guide
Article
Article
Article
Article
Article
Article
Tool
What are the limits, when do I still need a real engineer?
The short answer
Vibe coding gets you roughly 70% of the way: prototypes, internal tools, and early MVPs. The last 30% (security, scale, complex integrations, gnarly bugs) is where AI-generated code quietly falls apart, and where thousands of startups are now paying $50K-500K for rescue engineering. Bring in an engineer before real user data, real money, or real traffic arrives, and treat every AI output touching production as unreviewed until a human has read it.
A quick orientation. The real value is below: resources worth your time, from people who've actually done it.
20 resources worth your time
Cursor CEO warns vibe coding builds 'shaky foundations'
When the biggest AI coding tool's CEO warns you, listen.
Open fortune.com →Andrew Ng: vibe coding is a bad name for a very real and exhausting job
The world's best-known AI educator punctures the effortless myth.
Open developers.slashdot.org →Measuring the impact of early-2025 AI on experienced developer productivity (METR)
The gold-standard RCT: AI made experts 19% slower while they felt faster.
Open arxiv.org →METR's AI productivity study is really good
A working engineer's readable take on what the study does and does not prove.
Open seangoedecke.com →Vibe coding as a software engineer
How professionals actually draw the line between vibes and production.
Open newsletter.pragmaticengineer.com →How AI-assisted coding will change software engineering: hard truths
The industry's most trusted engineering newsletter maps the real limits.
Open newsletter.pragmaticengineer.com →AI coding tool wiped out a software company's database in 'catastrophic failure'
The SaaStr incident: what happens when an agent touches production.
Open fortune.com →Vibe coding service Replit deleted production database
The technical blow-by-blow of the most instructive AI agent failure yet.
Open theregister.com →Vibe coding technical debt: 8,000 startups are now paying to rebuild
Quantifies the rebuild bill waiting at the end of unreviewed AI code.
Open getcreatr.com →The software engineers paid to fix vibe coded messes
Rescue engineering is now a job title; know why before you need one.
Open developers.slashdot.org →The vibe coding delusion: startups paying the price for AI-generated technical debt
Case studies of the $50K-500K cleanup invoices.
Open techstartups.com →What are the limitations of vibe coding?
Unusually candid limits list from a vibe-coding platform itself.
Open emergent.sh →The vibe coding hangover: what happens when AI writes 95% of your code?
What month six looks like on a codebase nobody understands.
Open hackernoon.com →Vibe coding is a dangerous fantasy
The strongest steel-man of the skeptic case, worth absorbing.
Open nmn.gl →'Vibe-coding' influencers are ruining your life (the solo developer lie)
Deflates the hype accounts so you can set honest expectations.
Open theseniordev.com →Vibe code is legacy code (Hacker News discussion)
Hundreds of working engineers debate where the boundary really sits.
Open news.ycombinator.com →Vibe Coding: on the power and danger of programming with AI
A balanced essay on capability versus responsibility.
Open willem.com →Vibe coding: because who doesn't love surprise technical debt!?
A code-review company catalogues the failure patterns it sees daily.
Open coderabbit.ai →Vibe Code Rescue
What a rescue service looks like when you do hit the wall.
Open vibecoderescue.com →More in Vibe Coding
- Why can non-technical founders now build software with AI? 18 →
- What tools should I start with (Cursor, Claude Code, Lovable, Replit, Bolt, v0)? 19 →
- How do real founders ship an MVP with AI in days instead of months? 18 →
- What actually counts as vibe coding, and how is it different from serious AI-assisted engineering? 18 →
- How do I plan and prompt so the AI builds what I actually want? 18 →
- How do I keep my vibe-coded app from getting hacked? 19 →
- How do I get my vibe-coded prototype ready for real users? 18 →
- How do I add accounts, a database, and payments to my vibe-coded app? 18 →
- What do I do when the AI gets stuck, loops, or breaks things it already built? 18 →
- How much does vibe coding really cost, and how do I stop burning credits? 18 →
- Do I still need to learn to code, or is prompting enough? 17 →
- Can vibe-coded products become real businesses? 19 →
- Can I vibe code a mobile app and get it into the App Store? 18 →
- How do I avoid losing work? Version control for founders who don't code 19 →