4 ms·
This person wrote a series of books about clean code which are sometimes recommended to junior programmers. Some people have a high opinion of him. It's a good
by blub 9y ago
This person wrote a series of books about clean code which are sometimes recommended to junior programmers. Some people have a high opinion of him.
It's a good thing that his claims and experience are being questioned.
- carlmr 9y agoI read his books and they're pretty good in showing Junior developers better ways to structure their code. This doesn't mean that Uncle Bob is right on every topic. Safety critical software is completely out of his realm (at least I don't know of any project he worked on that's SC). From my own experience I've seen quite a few safety critical codebases and they're often abhorrent in lack of common sense software structure, precisely because there are so many regulations that you can't "quickly refactor" something, and in embedded systems there are too many mechanical engineers writing software, without caring about the craft.
- tptacek 9y agoWhat are some major projects he's worked on?
- blub 9y agoThey're not, he doesn't back up his recommendations with data, and instead expects readers to believe that they are appropriate and correct.
- carlmr 9y agoNeither do any other coding guidelines I've seen. What data do you want to gather about whether a name could replace a comment? It's like structuring an essay has a lot of rules, that you can break if you know what you're doing, but if you're just starting to write will help you be more clear in conveying your message. It's all subjective.
- mannykannot 9y agoFurthermore, some of his followers are very voluble and dogmatic in places like Stack Overflow/Exchange, driving out nuanced, reasoned discussions about how to improve software development.