

The principles are perfectly fine. It’s the mindless following of them that’s the problem.
Your take is the same take I see with every new generation of software engineers discovering that things like principles, patterns and ideas have nuance to them. Who when they see someone applying a particular pattern without nuance think that is what the pattern means.






This is crazy misattribution.
99% of code is too complicated because of inexperienced programmers making it too complicated. Not because of the principles that they mislabel and misunderstood.
Just because I forcefully and incorrectly apply a particular pattern to a problem it is not suited to solve for doesn’t mean the pattern is the problem. In this case, I, the developer, am the problem.
Everything has nuance and you should only use in your project the things that make sense for the problems you face.
Crowbaring a solution to a problem a project isn’t dealing with into that project is going to lead to pain
why this isn’t a predictable outcome baffles me. And why attribution for the problem goes to the pattern that was misapplied baffles me even further.