Senior developers across the tech industry are embracing vibe coding despite becoming what they call ‘AI babysitters’—spending significant time reviewing and fixing AI-generated code. This new reality comes with both productivity gains and unexpected challenges that are reshaping software development workflows.
What Exactly is Vibe Coding?
Vibe coding represents the practice of using AI assistants to generate code through natural language prompts. Developers describe their intent, and AI systems produce corresponding code. However, experienced programmers quickly discover that this approach requires extensive oversight. Consequently, they must verify every line of generated code for accuracy and security.
The Babysitting Reality of AI Programming
Senior developers report spending 30-40% of their time reviewing and correcting AI-generated code. Common issues include:
- Hallucinated package names and dependencies
- Security vulnerabilities from quick rather than proper solutions
- Redundant code implementations across different modules
- Missing critical components and edge case handling
This verification process has become so extensive that some companies are creating dedicated ‘vibe code cleanup specialist’ positions.
Real Developer Experiences with Vibe Coding
Carla Rover, a 15-year web development veteran, learned the hard way about vibe coding limitations. She spent 30 minutes sobbing after having to completely restart a startup project due to unchecked AI-generated code. “I handed it off like the copilot was an employee,” she admitted. “It isn’t.”
Feridoon Malekzadeh, with over 20 years in software development, compares the experience to “hiring your stubborn, insolent teenager.” He estimates his time allocation as: 50% writing requirements, 10-20% vibe coding, and 30-40% fixing AI-generated code.
Security Concerns in AI-Generated Code
Austin Spires, Senior Director of Developer Enablement at Fastly, notes that vibe coding often prioritizes speed over security. AI systems tend to build what’s quick rather than what’s right, introducing vulnerabilities similar to those made by novice programmers.
Mike Arrowsmith, CTO at NinjaOne, warns that vibe coding creates new IT and security blind spots, particularly dangerous for young startups. His company counters this with “safe vibe coding” practices including access controls, mandatory peer review, and security scanning.
The Productivity Paradox of Vibe Coding
Despite the babysitting requirements, developers report net positive results. A Fastly survey found senior developers were twice as likely to use AI-generated code in production compared to juniors. They acknowledge the extra review time but value the overall acceleration.
Malekzadeh summarizes the trade-off: “Every technology carries its own negativity, which is invented at the same time as technical progress. The pros far outweigh the cons.”
The Future of Developer Roles
As vibe coding becomes mainstream, developer roles are evolving. Elvis Kimara, a recent AI graduate, observes: “We won’t just be writing code; we’ll be guiding AI systems, taking accountability when things break, and acting more like consultants to machines.”
This shift requires new skills in AI supervision, code validation, and system thinking—areas where human expertise remains irreplaceable despite advancing AI capabilities.
Frequently Asked Questions
What is vibe coding?
Vibe coding refers to using AI assistants to generate code through natural language descriptions rather than traditional manual programming.
Why do developers call it AI babysitting?
Developers must extensively review, correct, and verify AI-generated code, similar to supervising a inexperienced junior developer who requires constant oversight.
Is vibe coding secure for production use?
Not without thorough review. AI-generated code often contains security vulnerabilities and requires human expertise to ensure proper implementation and security standards.
Does vibe coding actually save time?
Yes, but with caveats. While AI accelerates initial code generation, developers spend significant time reviewing and fixing the output, resulting in net time savings for most experienced developers.
How are companies addressing vibe coding challenges?
Progressive companies implement “safe vibe coding” practices including access controls, mandatory peer reviews, security scanning, and sometimes dedicated code cleanup specialists.
Will vibe coding replace human developers?
No. It changes their role from pure coding to AI supervision, system architecture, and quality assurance—areas where human judgment and expertise remain essential.
