Vibecoder Breaks Production. Company Defends Firing 5,000 People.

A software company that replaced 5,000 employees with a small team of vibecoders has defended its AI strategy after a production update made the company’s entire product stop working.

Executives said the incident demonstrated how quickly the new team could deliver meaningful change. Before the restructure, a failure of this size would have required coordination across several departments. This one was completed by a 24-year-old named Ethan, working alone, shortly before lunch.

“We’ve removed an enormous amount of friction,” said the company’s chief executive, standing in an office large enough for considerably more employees than were currently employed. “The previous organization would have asked a lot of questions before shipping something like this. Today, Ethan was able to trust his instincts and move.”

Ethan’s instincts were largely supplied by a chat window. He had asked it to make the checkout faster, and it had responded by removing the part that checked whether people were allowed to check out. A subsequent attempt to restore that feature deleted the settings page. The company is still establishing why customers can now change the chief financial officer’s profile picture.

The update passed the new quality-assurance process, which involved Ethan asking whether the code looked good and receiving an enthusiastic answer. He then asked whether it looked really good, adding that the CEO was excited to get it live. The answer became more enthusiastic.

A senior director said this represented a more collaborative relationship with technology than the former testing department’s habit of explaining what was wrong. Several of those testers were among the 5,000 employees whose departures the company had described as an opportunity to focus on higher-value work, elsewhere.

Management has rejected suggestions that the layoffs contributed to the outage. It said the company now had more than enough capacity to identify the problem because the people remaining were responsible for everything. One of them had already identified a problem with this arrangement, but the reporting form was part of the product.

Ethan initially attempted a rollback by asking the model to put things back how they were. It produced a thoughtful apology and a redesigned dashboard. When he clarified that he meant the working version, it renamed a variable to workingVersion and assured him that the underlying issue had been addressed.

The board was briefed on the incident using a slide showing a 97 percent reduction in engineering headcount. The next slide, which showed a 100 percent reduction in customers being able to log in, was described as a temporary engagement anomaly. Both figures were technically improvements in the direction the arrows had been drawn.

The chief executive said it was unfair to judge the company’s investment by a single afternoon of customers being unable to access the thing they paid for. The company had judged the continued employment of 5,000 people using a considerably shorter demonstration, during which an AI assistant created a colorful to-do list.

A former engineer who recognized the error message offered to explain the failure. Human resources asked whether he would be open to returning on a six-week contract. He said he would be open to being paid. The conversation has been escalated to procurement, where the relevant specialist’s position was eliminated in the same round.

Customer support has meanwhile been instructed to emphasize the speed of the response. Tickets are now acknowledged in under a second by a system that apologizes, suggests clearing the browser cache, and marks the issue resolved. One customer received 38 apologies before a human representative could locate a chair.

During an all-hands meeting, the CEO thanked Ethan for being brave enough to ship. Employees were encouraged to remember that failing fast was central to the culture, although the people asking whether the website should work were advised to bring a more constructive attitude. The meeting ended with an invitation to submit ideas for restoring service.

Ethan has since found a folder labeled backups. Nobody is certain what it contains because the person who named it has lost access to the building. Management has asked him to avoid opening it until communications can establish whether doing so would create the impression that the old team had been doing anything useful.