For example I saw the agent advise someone to introduce a soft delete mechanism into their database schema, thus incurring all the query performance, correctness and maintenance headaches that come with it, even though they didn’t actually use soft deletes to support any product feature. (And indeed the change had plenty of latent defects because the soft delete pattern hadn’t even been correctly implemented.) We talked about it, and it sounds like he had just uasked, “Should I include soft deletes?” And it just gave him a generic trendsloppy answer about how soft deletes are often considered a best practice. He was more of a full stack developer with relatively shallow database knowledge, so he couldn’t see that this was at best half an answer. If he had gone to Google instead, though (and perhaps also scrolled passed the LLM slop that clutters the top Google results these days), he would have had a decent chance of finding a more nuanced article that could have helped him build a deeper understanding of the tradeoffs so that he could make a more informed decision.