Unpopular opinion: some of you think models get enshittified because you built a system without resilience and heavy testing, and then blame it on the model when it breaks three weeks later
retained text
Title. After having managed business systems for a couple of years now, relying pretty heavily on coding agents to do so, I've lately been reflecting on the importance of the less "flashy" things that are becoming increasingly easy to forget in the age of AI. I mean the things like system resilience, testing. The "boring things." It is so easy to stop holding code to a high standard and just ship on YOLO mode... and then blame the model. Code is still code. The system built with AI, shipped without heavy testing, that then failed in production is the same system that would have been built *by hand*, shipped without testing, and then failed in production 20 years ago. AI is a tool with limits. It's both a product and a tool. There are legitimate reasons to not place blind trust in a product, and model regressions are real. But people may point the finger too much at the product, ignoring how it's being used. They may not reason about the edge cases that bite in production weeks later. And when they do bite, the same person blindly tells Claude, "fix it no mistakes." The model attempts to fix it inside a bloated, unorganized codebase. It of course breaks, making it *feel* like the model got worse. Then they come and post: "Is Opus 5.5 dumb as shit now?" Good engineering practices are still good engineering practices, AI or not.
document fetched 2026-11-15 00:35 · canonical https://reddit.com/r/ClaudeCode/comments/1xvwd6a/unpopular_opinion_some_of_you_think_models_get