Comment by thrower123
5 years ago
Clean Code is fine. It's a little dated, as you would expect, and for the most part, everything of value in it has been assimilated into the best practices and osmotic ether that pervades software development now. It's effectively all the same stuff as you see in Refactoring or Code Complete or Pragmatic Programmer.
I suspect a lot of backlash against it centers around Uncle Bob's less than progressive political and social stances in recent years.
I never read Clean Code and know nothing about its author so I'm willing to trust you on the first part, but the second paragraph is really uncalled for IMO. The article is long and gives precise examples of its issues with the book. Assuming an ulterior motive is unwarranted.
I don't think it is uncalled for when there have been several instances of boycotts organized for that reason.
Nobody is that upset about anodyne OOP design patterns
TFA really seems to be saying that there's no such thing as clean code, so don't even bother trying.