It may not be possible for us to ever reach empirical definitions of "good code" or "clean code", which means that any one person's opinion about another person's opinions about "clean code" are necessarily highly subjective. I cannot review Robert C. Martin's 2008 book Clean Cod...
ugh yes. I’ve seen so much painful code at work because of overDRYing and people trying to extract things just because of length (at the expense of coherent readability) and… it just doesn’t have to be this way.
(same way with design patterns: maybe they should start out being introduced with “if you see awkward looking code that looks like this, then consider this pattern” rather than the overly abstract “this pattern can be applied to this situation”… so many singularly implemented interfaces 😤)
This is a never ending nightmare in my job as well. How, having to ctrl + left click function after function all over a file to figure out what one particular function is doing increases readability or understandablity is beyond me. When I brought all this up I got this book as a reply…