“What would happen if you allowed a bug to slip through a module, and it cost your company $10,000? Hope you enjoy it.īeing a professional means taking full responsibility for one’s actions. So please go ahead to read the book first to ensure you yield the most learning. This summary is solely based on my filtered eyes hence could be used mainly for a quick reference after you have read the book at least once.

The book contains 14 chapters provides guiding principles to be an outstanding developer. The Clean Coder is definitely one of the best books I've read about Software Development, and I'm adding it to my favorites.Clean coder is one of the classical book that every developer should read written by Robert C. He has similar advises, but about how you should write code. Uncle Bob is like your doctor who is telling you that you should eat healthy and exercise regularly. Ohh.and if you have never heard about Uncle Bob checkout Every Uncle Bob Robert C Martin Video playlist on youtube, his blog, and SOLID principles. It is a great summary and advice on common wrong doing of most programmers that is not caused by their lack of proficiency, but rather not sticking to their professionalism and discipline. If you don't want to read entire book, read first 3 chapters. It would cost me 1 day, but I would save 2 days I spent fixing the bug this test would guard against'? I'll let you to deal with the answer. I would save a day'? What about situation like: 'Damn, I wish I did add that test. However, I have an impression that a lot of people are able to get away with that.ĭo you remember a situation when you thought: 'Damn, I wish I didn't add this test. There is nothing worse than giving false promises just to make others happy. Be professional and responsible, while being polite. In Clean Coder, Uncle Bob is explaining by example how to communicate at work. Such as underestimating time, undergo management pressure or cutting corners (AKA writing bad code). What's more, it demonstrates how to avoid common pitfalls in software development process. It's about how to behave professionally, be disciplined, and stick to good coding practices. While Clean Code is about good engineering practices, and writing good code, The Clean Coder is more about communication aspect of developer's work. You are probably familiar with Uncle Bob's classic: Clean Code.

The clean coder