Clean Code

“I liked the book, so did my colleagues, and we even had a meetup to discuss the book”

“pretty useful as a drop in solution”

“CleanCode is open source under the MIT license”

“some of the principles might be out of date, wrong, or overkill”

“consider naming and writing your functions in such a way that doesn't require a wall of comments”

“it is actually a well-written book”

“I like how at least he tried. I've been a fan of his for awhile but I'm not big on objects”

“in large part because of efforts like "Clean Code" putting bugs in ears”

“There is still good meat-on-the-bone in the book, and especially interesting if you're working in a legacy system from that older time and place.”

“i'd argue it is even more harmful for beginns, i remember we had to code a chess program and seeing students getting stuck on OOP stuff rather than actually solve the problems.”

“I think you've missed the point of clean code if this is your gripe with it.”

“Even Robert Martin, very often in his videos and blogs, espouses "engineering judgment" and is quite fine abandoning advice in his book when the situation calls for it.”

“extensively revised to account for the many misconceptions which new programmers might have gotten from the old edition”

“Your code is bad or slow - not the programming principles.”

“Mature programmers know that the idea that everything is an object is a myth.”

“it is empirically worse for performance, and that trade off matters for many use cases”

“The book is written by someone with a very limited experience and the advice is either basic and obvious or harmful.”

“Clean Code is unhelpful to beginners too, though: misuse of industry-standard terms, shunning of comments in favor of tiny functions with long names”

“So they hate clean code because they don't actually know clean code”

“It is not without merit, but tends to attract the tedious killjoys and midwits.”

“it's that length code with many branching conditions is prone to be untestable and introduce non trivial bugs”

“Clean Code has some useful things, but it is a collection of one person's judgements (some good, some bad)”

“helpful for early developers who need some structure, but harmful to late-stage developers who adopt it as dogma”

“when I read it as a newbie it was really helpful”

“some other guy would distill some patterns, market another book with a catchy title that'd be inevitably somewhat misunderstood and misused”

“didn't think it was mind blowing, but I used the parts that made sense and left the parts that didn't”

“found it revealing, but also annoying in parts”

“the amount of abstractions Uncle Bob advises makes it just too easy to make the code extremely hard to optimize later”

“he doesn't seem to have been very good at implementing them, and he often does so in ways that contradict other principles”

“The examples in Clean Code show that Uncle Bob himself misunderstood heuristics as strict rules that are to be taken to the extreme.”

“Clean Code has its really "meh" areas, but the core idea and spirit of it is sound”

“The whole point of 'Clean Code' is to establish a body of ethics software 'engineers' collectively agree to”

“People who read Clean Code as their first programming but and made that their identity have been the bane of my existence as a programmer.”

“Mr. Martin honestly just doesn't seem very good at implementing his ideas and getting the benefits that he anticipates from them.”

“It was written in different times, different audiences.”

“his reasoning, that 6 lines is too long, was a reflection of his desire to get every function as short as possible”

“I have had so many discussions about that style where I tried to argue it wasn't actually simpler and the other side just pointed at the book.”

“The world would be a better place if Philosophy of Software Design would replace all mentions of the second book.”

“famous for making bad suggestions and producing unreadable code with too many functions just for the sake of following its rules”

“it's Java centric and has a lot of questionable tips”