. Você pode encontrar resumos e versões digitais em plataformas como: Clean Code: A Handbook of Agile Software Craftsmanship
The name of a variable, function, or class should tell you why it exists, what it does, and how it is used. If a name requires a comment to explain it, then the name has failed to reveal its intent.
public int calculate(int a, int b, String op) if (op.equals("add")) return a + b; if (op.equals("sub")) return a - b; return 0;
The core principle of Clean Code is the reduction of cognitive load. As software systems grow in complexity, the primary cost of development shifts from writing new features to maintaining existing ones. Clean code minimizes this cost by using meaningful names, small functions, and clear logic. When a developer names a variable d instead of daysSinceCreation , they save a few keystrokes but lose minutes or hours of collective team time later when someone has to decode that ambiguity. Uncle Bob argues that code should read like well-written prose, where every function leads logically to the next, and the intent of the author is unmistakable.
