Sign in with Facebook
Code Quality Books
Showing 1-13 of 13
Refactoring: Improving the Design of Existing Code (Addison-wesley Object Technology Series)
by (shelved 4 times as code-quality)
avg rating 4.24 — 8,854 ratings — published 1999
Code Complete: A Practical Handbook of Software Construction (Paperback)
by (shelved 3 times as code-quality)
avg rating 4.30 — 9,488 ratings — published 1993
Clean Code: A Handbook of Agile Software Craftsmanship (Paperback)
by (shelved 3 times as code-quality)
avg rating 4.35 — 23,554 ratings — published 2007
A Philosophy of Software Design (Paperback)
by (shelved 2 times as code-quality)
avg rating 4.21 — 4,609 ratings — published 2018
Working Effectively with Legacy Code (Paperback)
by (shelved 2 times as code-quality)
avg rating 4.14 — 4,682 ratings — published 2004
Code Health Guardian: The Old-New Role of a Human Programmer in the AI Era (Paperback)
by (shelved 1 time as code-quality)
avg rating 3.84 — 25 ratings — published
Head First Design Patterns (Paperback)
by (shelved 1 time as code-quality)
avg rating 4.30 — 9,038 ratings — published 2004
Unit Testing: Principles, Practices, and Patterns (Paperback)
by (shelved 1 time as code-quality)
avg rating 4.57 — 608 ratings — published
The Clean Coder: A Code of Conduct for Professional Programmers (Paperback)
by (shelved 1 time as code-quality)
avg rating 4.26 — 9,280 ratings — published 2011
Clean Code in Python: Refactor your legacy code base (Paperback)
by (shelved 1 time as code-quality)
avg rating 4.08 — 131 ratings — published
Beyond Legacy Code (Paperback)
by (shelved 1 time as code-quality)
avg rating 3.86 — 101 ratings — published 2015
Game Programming Patterns (Paperback)
by (shelved 1 time as code-quality)
avg rating 4.49 — 1,593 ratings — published 2011
Agile Software Development, Principles, Patterns, and Practices (Hardcover)
by (shelved 1 time as code-quality)
avg rating 4.25 — 1,319 ratings — published 2002
“Tests shouldn’t verify units of code. Instead they should verify units of behavior: something that is meaningful for the problem domain and ideally something that a business person can recognize as useful. The number of classes it takes to implement such a unit of behavior is irrelevant. The unit could span across multiple classes or only one class, or even take up just a tiny method. [...] A test should tell a story about the problem your code helps to share, and this story should be cohesive and meaningful to a non-programmer.”
― Unit Testing: Principles, Practices, and Patterns
― Unit Testing: Principles, Practices, and Patterns
