The book is divided into three parts. The first describes the principles, standards, and practices that govern the creation of clean code. The second includes many case studies that gradually become more challenging. Each case is an exercise in "tidying up" code, that is, streamlining a problematic code base and transforming it into efficient and reliable code. The third part is the culmination: a single chapter containing a series of exploratory (heuristic) criteria and "intuitive signs" derived from the case studies. The result is a set of knowledge that describes our way of thinking when writing, reading, and cleaning software code.

The book will help you understand: How to distinguish well-written from poorly written code, How to write good code and improve bad code, How to create proper names, functions, objects, and classes, How to format code so it is as readable as possible, How to implement error handling methods without obscuring the code logic, How to perform appropriate unit tests and develop code guided by test results.

This is a book that is the alpha and omega for every programmer, software engineer, software project manager, programming team leader, and systems analyst who is involved in developing better code.

Contents: Clean Code, Meaningful Names, Functions, Comments, Formatting, Objects and Data Structures, Error Handling, Boundaries, Unit Testing, Classes, Systems, Emergent Design, Concurrency, Sequential Improvement, Inside JUnit, Refactoring the SerialDate Class, Exploratory Criteria and Intuitive Signs.