3 ms·
IMO many programmers simply don't like Clean Code because their greybeard mentors have been bothering them with it too much. They want something fresh and new,
by misja111 5y ago
IMO many programmers simply don't like Clean Code because their greybeard mentors have been bothering them with it too much. They want something fresh and new, something that makes them feel they understand software development better than most of their peers including their mentors.
- pydry 5y agoClean Code was horribly dogmatic. He would lay down "laws" that were actually trade offs that worked well for him in specific instances in the past, blithely lacking understanding of the context that made them work. The danger with Clean Code is that a lot of the advice would work a lot of the time so it's very easy to think it's exactly on point right up until it guides you face first into a brick wall.
- Jtsummers 5y agoExcept it isn’t dogmatic. Re-read chapter 1 where they write that there is not One True Way and advise the reader to go find other sources along with reading their own book. That is not something dogmatic writers would include.
- pydry 5y agoYeah, then skip to the chapter on TDD where he lists the "laws" :/
- Jtsummers 5y agoAgain, read the first chapter. A dogmatic text would not tell you to go find and study other sources and develop your own path. That they then tell you their ideas in an opinionated fashion is not in (total) conflict with that sentiment. The claims of dogma are, in my opinion, grossly exaggerated and a consequence of people failing to read (or failing to comprehend) the authors' own caveats in chapter 1. If they didn't include those statements in chapter one, maybe I'd agree with you. I still wouldn't discard the text out of hand, because, you know we have brains and can think critically and read a text to evaluate it ourselves. (I say "authors" because Bob Martin was the primary author, several chapters are written by other people.)