Download Clean Code A Handbook of Agile Software Craftsmanship Robert C Martin Series 1 Robert C Martin eBook

Product details File Size 41903 KB Print Length 464 pages Simultaneous Device Usage Up to 5 simultaneous devices, per publisher limits Publisher Prentice Hall; 1 edition (August 1, 2008) Publication Date August 1, 2008 Sold by  Digital Services LLC Language English ASIN B001GSTOAM

Clean Code A Handbook of Agile Software Craftsmanship Robert C Martin Series 1 Robert C Martin eBook Reviews

• I've been programming about 17 years and consider myself above average programmer. Yet, this book made me feel like I'm actually horrible coder. I've always gotten my tasks done but I didn't pay attention on refactoring to clean up the code. I'm already behind and got a demo coming up in few days. As I'm reading my guilty verdicts on all his 'bad code' examples, it inspire me to care about 'coding' yet again. It can be fun and it's not all about getting the job done. What's sad about the reality is that 'bad code' will continually increase over time because people don't realize what 'bad code' can do in the long run.
  
  Every programmer regardless of experience should read this book. Thanks!
• 3.5 stars. I'm rounding up.
  
  Much of the information in this books is eye opening, particularly the chapters on functions, classes, and code smells. However, a serious problem is that this book is very, very Java-centric, and it is clearly a product of its 2009 copyright date. Many of the chapters have been made moot (PEP8 and Prettier making the formatting chapter largely obsolete, for example), and a few aren't totally applicable to any other language.
  
  Note about buying a new, physical version from don't. The book will be damaged in shipping as it just comes in a padded envelope and will be dog-eared like a used book before you receive it. See my picture.
• I've been reading this for the past few weeks and just by applying the principles and concepts I've learned so far, I've become a better and more mature developer. The lead dev on my team recently noticed and commented on the positive changes in my code as of late. He was also impressed when I used what I learned to refactor a bit of our code base. Even though it's Java-based and I am a Go developer with a background that is primarily JS, I've been able to use the ideas in this book to clean up my own code, both personally and professionally.
• This is a critical thinkers book. It gives the reader a basis to use within their own programming style and language of choice.
  
  The code examples are written in Java and are there to show how to refactor code based on the principles and reasoning within the book.
  This is not a book that I take as a specific do this or else, more of a guide that explains why you should consider writing code in the way described.
  
  Essentially the lesson is to create code that is small, has a specific purpose and does that one thing.
  When functions or methods begin to stray into doing multiple things spin those code pieces off on their own and repeat.
  
  What I get from this book is a mindset or way of thinking about programming. To create code that is cohesive, is small, does not have unnecessary parts. When these principles are broken find a way to refactor or eliminate the additional pieces. It is not just about taking away or keeping code small but adopting a way of thinking about the design of the program and how each piece interacts with the other parts.
  
  The suggested line lengths of functions mentioned and other very specific examples is more where your critical thinking comes into play. I do not program in Java so many of the language specific scenarios do not apply to me. in some languages you just can't have or do some of the things suggested. Though as a general rule of thumb I find the examples helpful and when I mean general rule of thumb I do not mean a specific line count or size but a simplistic do as little as possible to achieve the goal. Simplify. Simplify. Simplify.
  
  I purchased and received the 16th printing of this book, published February 2016.
  There are no weird formatting or printing issues with the book as others have mentioned.
  
  If you have the ability to reason and think critically, being able to adapt examples and suggestions to your own style and language then I highly recommend this book. The contents are NOT common sense and do not come naturally to the uninitiated. The book does take you by the hand in a certain way leading you from the process of just make the program work to thinking about the logic design and function of your programs.
  
  When you are in situations where redesign is not possible the principles learned from this book will help you to refactor when possible and write new code that is better, smaller, tighter. Making you a better more valuable programmer.
• The content is good, but the soft cover version of the book is of a poor print quality, it looks like it was printed from photocopies.
  I heard that originally, the print quality was ok, well, it's not anymore.
  It's still readable, but I would never buy it if I new about the print quality.
  Should've read other reviews.
• Bought the book due to a push at work to read this, the book was bought through Services, Inc. and like others have said I received a copy with huge margins on each page, a blurry cover, and no spine or back. I didn't have any of the problems of the binding falling apart yet, the text is readable its just the code samples are a bit hard to read.
• Profoundly changed how I approach coding. I've been coding professionally for 10 years and felt as if I was in a rut and ran into the same issues multiple times.
  
  Clean Code goes into the depths of the problem. Robert Martin takes you through pages upon pages of code to make the points clear and relevant to real world problems. Too many books give simple examples that are difficult to make meaningful.
  
  Overall this is a great book that I recommend to programmers at all levels. You will learn something new (even though it's an "older" book).
• Stay far away from this book of you are not an OOP programmer. All examples are in Java but most C++ programmers should be able to mentally translate the ideas. There is also too much focus on Java specific tooling. While there are some good points this book makes, it disregards many good programming techniques used in standard imperative languages without objects. It completely disregards functional languages and given gives some terrible advice when it comes to writing good code in a functional style. Overall it's pretty good up to about chapter 7. After that it's pretty much downhill.