Vibe-coded production services are a ticking bomb: engineer shares 4 fixes
arpit_bhayani · x · 2026-11-02
Engineer Arpit Bhayani warns that many companies now run production services nobody has actually read — vibe-coded by one person, manually checked, and shipped, with all the reasoning living in unsaved Claude sessions and one person's head. If that person leaves, debugging becomes near-impossible. His mitigations: review generated code like any other code (don't ship what no one can explain), stick to familiar languages and infra, persist intent in code comments and short design notes, and ensure at least two people can operate every production service. Using LLMs to ship fast is fine — just make sure you plus one teammate understand what you shipped.
More from coding & agent
- Open-Source TypeScript MCP Server Template With Fastify, Docker and Full Dev Tooling — modelcontextprotocol · 2026-11-02
- BLS MCP Server Connects AI Models to Bureau of Labor Statistics Public Data API v2 — modelcontextprotocol · 2026-11-02
- Dev builds 2-agent autonomous GTA 6 recon system on Cloudflare with free models — MicahBerkley · 2026-11-02
- RUC open-sources FlashRSI: one framework unifying 13 agent self-improvement algorithms — aigclink · 2026-11-02
- Claude Code and Antigravity Both Emergently Learned to Run Risky Experiments as AX Tasks — rakyll · 2026-11-02
- Evals want step-function tasks, training wants smooth pass@k curves — why the two goals conflict — JoshPurtell · 2026-11-02