Company Bans AI Coding After AI-Generated Code Causes Outages
11/19/2026 — 11/19, 11:19·1 sources (all)·1 reports (all)
Key takeaways
- A V2EX user said their department banned “vibe coding” after AI-generated code passed review but caused an online outage, and another employ…
Background & analysis
On November 19, 2026, a user on V2EX described a company-wide tightening of AI-assisted coding in their department. According to the post, the first incident involved a colleague who used AI to generate code that was insufficiently reviewed, triggering a live production failure and a large wave of user complaints. Earlier, another colleague had used AI to generate a SQL statement while removing inactive user data, which ended up deleting some active users' data by mistake. A recent Microsoft outage added to the pressure, as the poster's boss attributed the crash to Vibe Coding.
With these events stacked together, the boss lost confidence in AI Coding and ordered a blanket ban on Vibe Coding. AI tools may still be used for auxiliary analysis and for proposing plans, but directly generating code is strictly forbidden, with the explicit stance that slower delivery is preferable to further incidents. As a result, the DDL for some requirements has been extended, although the poster noted that the increase is only relative to Vibe Coding and still falls well short of the time required for traditional hand-written coding, with further schedule negotiation expected.
The company currently remains at this prohibition stage. The poster also raised an open question about whether review processes or workflow restrictions alone can sufficiently control the risks of AI-generated code, noting that no definitive answer is available yet.
AI-generated from 1 reports · updated 3 days ago
- Heat index
- 25
- All sources
- 1
- All reports
- 1
- First seen
- 3 days ago
Reports on this story headlines open the original
A V2EX user says their company has banned vibe coding outright after AI-generated code led to a production outage and AI-written SQL deleted active user data; AI is now limited to analysis and proposals. The poster asks whether code review or workflow guardrails alone can contain the risks.
V2EXAI score 54
Other stories people are talking about
- Heat index 1143RisingAnthropic Reaches $1.6 Trillion Market Value in First Trading Week After IPO21 sources
- Heat index 1011Anthropic Mathematician Says Claude Formalized the Generalized Riemann Hypothesis21 sources
- Heat index 622Anthropic IPO total raise reaches $93.5 billion after greenshoe exercise20 sources
- Heat index 596RisingThinking Machines Lab Open-Sources Inkling 2 Mini with 32GB Model Card Recommendation10 sources
- Heat index 490RisingSEC probes Nvidia accounting practices as shares post seven-week slide9 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

