Why read Test Driven Development?

Book cover of Test Driven Development: By Example

Book description

Quite simply, test-driven development is meant to eliminate fear in application development. While some fear is healthy (often viewed as a conscience that tells programmers to "be careful!"), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who are unable to absorb constructive criticism. When programming…

Explore

Topics

Genres

Coming soon!

When you buy books, we may earn a commission that helps keep our lights on (or join the rebellion as a member).

Why read it?

1 author picked Test Driven Development as one of their favorite books. Why do they recommend it?

Jan Van Ryswyck

Author

During the early years of my career as a software developer, I regularly developed very small programs that would exercise parts of the system that I was working on back then. I realized very quickly that those small programs would save me a lot of time figuring out whether the changes that I made would actually work or not. Until at some point a colleague mentioned the concept of Test-Driven Development. I first did some experimentation, dipping a toe into the water to feel the temperature. It wasn’t until the first time I picked up this book that I jumped…

From Jan's list on The best books to start your software developer journey with Test-Driven Development.