Senior developers are spending up to 40% of their time fixing AI-generated code as 'vibe coding' transforms the industry. A new Fastly survey reveals 95% of nearly 800 developers dedicate extra hours to debugging AI output, with the heaviest burden falling on experienced programmers who've become reluctant 'AI babysitters.'
Carla Rover spent 30 minutes crying after her AI-generated code project collapsed. The 15-year web development veteran had trusted her AI coding assistant too much, skipping manual reviews in her rush to build a startup that creates custom machine learning models for marketplaces. When she finally audited the code, the errors were so extensive she had to restart the entire project.
'I handed it off like the copilot was an employee,' Rover told TechCrunch. 'It isn't.'
Rover's experience reflects a growing reality across the tech industry. A recent Fastly survey of nearly 800 developers found that 95% spend extra time fixing AI-generated code, with senior developers bearing the heaviest verification burden. The phenomenon has given rise to a new corporate role: 'vibe code cleanup specialist.'
The numbers tell the story of an industry in transition. Feridoon Malekzadeh, who's building his startup using the vibe-coding platform Lovable, estimates spending 50% of his time writing requirements, 20% on actual vibe coding, and 30-40% on 'vibe fixing' - debugging the unnecessary scripts and bugs created by AI.
'You have to ask them 15 times to do something,' Malekzadeh explained, comparing AI coding tools to 'hiring your stubborn, insolent teenager.' 'In the end, they do some of what you asked, some stuff you didn't ask for, and they break a bunch of things along the way.'
The technical challenges run deeper than simple bugs. Austin Spires, senior director of developer enablement at Fastly, notes that AI code prioritizes speed over security, introducing vulnerabilities typically made by novice programmers. The tools struggle with systems thinking, creating redundant solutions instead of reusable components.
'If you're creating a feature that should be broadly available, a good engineer would create that once and make it available everywhere needed,' Malekzadeh said. 'Vibe coding will create something five different times, five different ways, if needed in five different places.'
Security concerns compound the problem. Mike Arrowsmith, CTO at IT management company NinjaOne, warns that vibe coding creates new security blind spots, particularly dangerous for young startups. 'Vibe coding often bypasses the rigorous review processes that are foundational to traditional coding and crucial to catching vulnerabilities,' he noted.
