A lot of programmers today do read some bad summary of SOLID or GoF or whatever and then get confused or angry when things don't follow the models they're aware

A lot of programmers today do read some bad summary of SOLID or GoF or whatever and then get confused or angry when things don't follow the models they're aware of. (It's not a recent phenomenon, you can see it with MVC 15-20 years ago too, but a lesser percentage of programmers today have the fundamental grounding to break out of it.) In particular I see new programmers struggle with the "shared format" puzzle (they want an answer, and there isn't one), and especially Java developers today are deep on the wrong side of the "inversion puzzle" continually mistaking DI for loose coupling and sound architecture. Does this article help? I'm not really sure. But does elevating shallow mostly-wrong lessons like Clean Code hurt, and we need to address that somehow? Absolutely.