2 results for “kentbeck”
6b. For some complex scenarios—such as testing behavior on a specific complex state to find an obscure bug—that may not be possible. Writing tests first really helps with this as it forces you to think about the behavior of your code and how you're going to test it before you write it.
Testing first encourages smaller, more modular units of code, which generally means better code. A good book for getting started with the "test first" approach is Test Driven Development by Example, by Kent Beck.
1b. YAGNI: "You Aint Gonna Need It". Don't write code that you think you might need in future, but don't need yet.
The same is true for commenting-out code; if a block of commented code is going into a release, it shouldn't exist. If it is code that may be restored, make a ticket and reference the commit hash for the code delete. YAGNI is a core element of agile programming. The best reference for this is Extreme Programming Explained, by Kent Beck.