A lot of people die on the hill of hating strongly typed languages as well.
People who write hard to understand and thus difficult to maintain code without possessing some self reflection skills will say anything negative they can about this book.
When having to declare something is a string or int or bool or whatever triggers people, then certainly having to stick to best practices (as deemed by the author), such as the single responsibility principle, is going to be nightmare for their habits.
Clean code is ultimately a treatise on how to not be a dick while working as part of a team.
It also reinforces this notion that software engineer has a craft component which really seems to rub some people the wrong way.
A lot of people die on the hill of hating strongly typed languages as well.
People who write hard to understand and thus difficult to maintain code without possessing some self reflection skills will say anything negative they can about this book.
When having to declare something is a string or int or bool or whatever triggers people, then certainly having to stick to best practices (as deemed by the author), such as the single responsibility principle, is going to be nightmare for their habits.
Clean code is ultimately a treatise on how to not be a dick while working as part of a team.
It also reinforces this notion that software engineer has a craft component which really seems to rub some people the wrong way.