Tidying up messy software is a must. And that means breaking up the code to make it more readable -- "tidying" the code to make it more understandable. In this practical guide, author Kent Beck, creator of Extreme Programming and pioneer of software patterns, suggests when and where you might apply tidyings in your code to improve it while keeping the overall structure of the system in mind. Instead of trying to master tidying all at once, this book lets readers try out a few examples that make sense for their problem. If they have a big function containing many lines of code, they'll learn how to logically divide it into smaller chunks. Along the way, developers will learn the theory behind software design: coupling, cohesion, discounted cash flows, and optionality. This book helps you: Understand the basic theory of how software design works, and learn about the forces that act on it Explore the difference between changes to a system's behavior and changes to its structure Improve your programming experience by sometimes tidying first and sometimes tidying after Learn how to make large changes in small, safe steps Prepare to design as a human activity with diverging incentives
Kent Beck Book order






- 2023
- 2015
Kent Beck's Guide to Better Smalltalk
- 428 pages
- 15 hours of reading
Targeted at Smalltalk programmers, this guide aims to enhance their effectiveness as developers and users of object technology. It provides insights and techniques tailored specifically for mastering Smalltalk, enabling readers to improve their programming skills and deepen their understanding of object-oriented principles.
- 2004
JUnit pocket guide
- 120 pages
- 5 hours of reading
JUnit, created by Kent Beck and Erich Gamma, is an open source framework for test-driven development in any Java-based code. JUnit automates unit testing and reduces the effort required to frequently test code while developing it. While there are lots of bits of documentation all over the place, there isn't a go-to-manual that serves as a quick reference for JUnit. This Pocket Guide meets the need, bringing together all the bits of hard to remember information, syntax, and rules for working with JUnit, as well as delivering the insight and sage advice that can only come from a technology's creator. Any programmer who has written, or is writing, Java Code will find this book valuable. Specifically it will appeal to programmers and developers of any level that use JUnit to do their unit testing in test-driven development under agile methodologies such as Extreme Programming (XP) [another Beck creation].
- 2002
Test Driven Development: By Example
- 240 pages
- 9 hours of reading
Follows two TDD projects from start to finish, illustrating techniques programmers can use to increase the quality of their work. The examples are followed by references to the featured TDD patterns and refactorings. This book emphasises on agile methods and fast development strategies.
- 2000
Extreme Programming Explained
- 224 pages
- 8 hours of reading
Describes how to improve your software development by integrating accountability, transparency and responsibility into your daily development process. This book helps you how to: involve the whole team; increase technical collaboration through pair programming and continuous integration; reduce defects through developer testing; and more.
- 1997
The CRC Card Book
- 290 pages
- 11 hours of reading
This concise book addresses the actual details involved with using CRC cards, including coverage of the team approach to analysis and examples of program code (Java, C++, and Smalltalk) derived from the use of the CRC card method.