The release date for the English version of 'Clean Code: A Handbook of Agile Software Craftsmanship' by
Robert C. Martin is Aug 2008. If you enjoy this novel, it is available for buy as a paperback from Barnes & Noble or Indigo, as an ebook on the Amazon Kindle store, or as an audiobook on Audible.
Even flawed code can work. However, unclean code has the power to destroy a development team. Each year, a great deal of time and money are wasted due to badly designed code. However, things don't have to be that way.
Prominent software specialist Robert C. Martin introduces Clean Code: A Handbook of Agile Software Craftsmanship, a paradigm-shifting work. Martin, together with his colleagues at Object Mentor, has combined their finest agile practices for code cleanup on the fly into a book that, with effort, will imbue you with the qualities of a software craftsman and improve your programming.
What kind of job are you going to be doing? There will be a lot of code that you read. You will also be asked to consider the positive and negative aspects of that code. More significantly, you'll be forced to reevaluate your dedication to your work and your professional ideals.
The three sections of Clean Code are separated. The first outlines the guidelines, conventions, and methods for creating clean code. A number of more difficult case studies make up the second section. Every case study is an exercise in code cleaning, in which a problematic code base is transformed into a reliable and effective one. The payout comes in the third section, which is a single chapter with a list of heuristics and "smells" discovered throughout the case study creation process. The end product is a knowledge library that explains our thought processes for writing, reading, and cleaning code.
After reading this book, readers will gain insight
How to produce excellent code and how to turn poor code into good code; How to distinguish between good and bad code; How to make good names, good methods, good objects, and good classes
How to include comprehensive error handling without impairing the logic of the code ‿ How to style code for optimal readability How to use test-driven development and unit testing
Any developer, software engineer, project manager, team lead, or systems analyst who wants to write better code has to read this book.