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.
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.
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.
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".
Which works in theory, in practice it's not that that easy, especially since UB seems to cater for the most "religious" ones
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.