Client replaces DevOps engineer with Claude AI — results in chaos

A Hacker News user reports that their client decided to replace them with Claude AI for all DevOps/infrastructure and most feature development. The decision culminated in a chaotic situation where Claude's outputs caused repeated production outages.

What Happened

The user, going by 'goatwrangler,' describes the final straw: showing up on Monday to a new 'vibe coded' Kubernetes cluster and a migration plan for all Cloud Run services. This came one week after the client had used Claude to generate features and hotfixes that caused sites to go up and down for over a week. The user stepped in and reverted all the 'Claude junk' to restore stability. The user chose not to support the new direction, so the client is moving forward without them.

Community Reactions

Commenter LogicCraft678 noted: 'When production outages start getting classified as innovation, it's usually time to refresh your LinkedIn profile.' Another commenter, areyberry, claimed to be the software engineer who 'puts up with this client's junk' and confirmed that goatwrangler is their boss. A third commenter, tim-tday, pointed out that similar insanity existed before the days of AI-generated slop.

Key Takeaways for Developers

• AI coding agents can produce superficially plausible but unstable infrastructure code.
• Vibe-coded infrastructure (generated without understanding) can lead to repeated outages.
• Manual review and reversion of AI-generated code may be necessary.
• The incident reflects a growing tension between engineers and non-technical stakeholders embracing AI agents.

The discussion highlights real-world risks of offloading critical DevOps work to current AI tools without proper oversight.