Never have I read a book so perfect and dead on, yet never have I so disagreed with it. He uses an antiquated notion of free will to justify the honing of the craft so that coders can serve the whims of the monied and/or powerful. Yes, if you do this you will be a better coder but you will never ...
Having read Clean Code, I started to apply many of its principles to my own coding and started to see a lot of value in proper naming and proper structure rather than "getting the job done".With that said, I wish there was a newer version using something other than Java. Perhaps Javascript, PHP, ...
Mostly this book is pretty good. It's a series of anecdotes from the author's lifetime of working in the software industry. They are reminiscent of things you might see on thedailywtf, but they are followed up with an explanation of what the correct response to each situation would be. This actua...
There's a lot of great material in this book, and it's probably worth a quick read for all developers. Younger developers would probably get the most out of it, since they have the most to learn, and the biggest habits to shape, but even seasoned developers can and should learn from the advice he...
The entire content of Clean Code is, or at least should be, common sense to the competent software engineer. Even though the average developer isn't likely to derive a whole lot of new knowledge from reading Clean Code, I consider it up there with the "classics" of software development literature...
The book is fantastic.. I have been programming in java for quite some time and I think i have been following some best practices. But the details of the book are an eye opener. Whether it is related to simple commenting, junits, accessor methods, classes or refactoring there was something new to...