Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, c
942 65 4MB
English Pages 431 Year 2009
Table of contents :
Content: Clean code --
Meaningful names --
Functions --
Comments --
Formatting --
Objects and data structures --
Error handling --
Boundaries --
Unit tests --
Classes --
Systems --
Emergence --
Concurrency --
Successive refinement --
Junit internals --
Refactoring serialdate --
Smells and heuristics.