"I don't care if the app is a synchronous multi-page form with zero no need for websockets. It must have them!" (because it says so on my slide)
Not having that, I developed the knowledge myself through trial and error, but we would have saved a lot of time, money, and stress doing it right the first time.
In general, I think this kind of “architect bad” take underestimates the cost and the stress of being responsible for a system that ultimately isn’t a great fit for the domain, and needing to balance hacking another fix onto it vs migrating to what now know is the right thing.
Sounds exactly like the kind of intuition an LLM will have.. "best practice" that's really whatever fads/marketing hype that there is a lot of noise about, never been informed by experiments or pain.
There was a post complaining about AI preference for god objects earlier, but the thing about stuff like that is, you could mechanically disincentivize it purely from complexity metrics or ASTs, either in training, or at the agentic layer later. I'm really much more worried about when LLMs are flooding the internet with marketing, and LLMs are consuming the marketing to determine best practice