Elon Musk retweeted a long post from an engineer, replying with just one word: "bad." The poster, who joined a large tech company two weeks ago, stated that specifications, code, testing, product requirements, work orders, closures, and reports are all generated by Claude Code. The team does not like this but is pressured to deliver as much as possible.

He wrote that superiors repeatedly say submitting code is no longer a bottleneck, yet still question why progress is slow. Engineers work 12 to 13 hours a day, primarily interacting with the model and hitting enter. From junior to L7, positions are reduced to the same task: talking to Claude. No one reads the code, fixes defects, or experiences the satisfaction of solving problems.

He does not oppose using models but requests at least time to verify the code flow. The current goal is framed as just getting things online, regardless of the consequences. The post quickly surpassed three million views, with likes and shares amplifying, turning the unnamed large company's workspace into an industry public sample.

Musk did not name the company or provide a comparison to his own factories or xAI's processes. The incremental information he provided marked this situation as bad: it is not that models cannot write code, but that people have withdrawn from reading, testing, and thinking, leaving only management pushing for delivery and hours spent hitting enter.

The poster simultaneously expressed a desire to leave but felt it would be the same elsewhere. The environment is described as creativity giving way to output volume, with possibly no one in the codebase able to explain what each piece of code does.

From a market mechanism perspective, this narrative impacts valuation stories. Buyers continue to bet on the penetration of AI programming tools, cloud vendor tokens, and the efficiency myth of tech stocks; sellers worry that unattended code will increase accident, rework, and regulatory costs. Capital flows towards model invocation and "efficiency" narratives. Beneficiaries are programming agent suppliers; those under pressure are the positions that treat engineer hours as quality assurance.

Source: Public Information