3 ms·
Clean Code Series from Uncle Bob. The books made me realize how horrible my codes are. No matter how long you've been programming, I think these books should b
by sus_007 9y ago
Clean Code Series from Uncle Bob.
The books made me realize how horrible my codes are. No matter how long you've been programming, I think these books should be read by every single programmer out there.
- BoorishBears 9y agoI wish they hadn’t. Clean Architecture is a plague on Android development undoubtedly unleashed by some obscure IDE programmer paid by the number of times you use the “Go To Definition” function.
- raverbashing 9y agoCC seems to be Design Patterns meets Moral Harassment It turns development teams into a judgemental arena, demeaning of other colleagues and a race to see who follows "the gospel" closer to the letter Who says their code is clean? Who says that's the best way of doing things? In all cases? It just reeks of "I'm better than the rest", which is already a problem in the industry.
- fdw 9y agoWhile I agree that can devolve into a dogmatic belief system, I also think that that's partly a people problem. Many of the ideas in Clean Code make code more readable (for example small methods, each containing only one level of abstraction; or good naming). It's on the coders to know how far to take these ideas and when to be pragmatic and say "good enough".
- raverbashing 9y ago> It's on the coders to know how far to take these ideas and when to be pragmatic and say "good enough". Which works in theory, in practice it's not that that easy, especially since UB seems to cater for the most "religious" ones
- fdw 9y agoIt isn't easy, but so far I've had luck with my co-workers. If they were more dogmatic, I think I would see Clean Code more critical too. But as it stands, I still recommend the book to new colleagues, and our culture takes care that we don't follow each "law" to its letter.
- raverbashing 9y agoYes isn't easy, that's why I'd rather avoid it