Debug Driven Development

Coding Philosophy

Samuel Taggart

Dec 16, 2020 • 1 min read

Recently on episode 5 of the DQMH podcast, Chris interviewed Joerg of Hampelsoft. There was a lot of good conversation, but one of the things that stuck with me was the idea of Debug Driven Development. That is writing code in such a way that it is easy to debug when things go wrong.

I think debugging is very important, but how do you do Debug Driven Design (DDD)? Just like Test Driven Development is about writing the tests first, DDD is about putting the debugging hooks in place first. This means having logging and error handling system in place first before you start building out your application. Then as you are building it, debugging becomes trivial.

Writing logging and error handling capabilities first is something I have always strived to do, but I never really had a name for it. Thanks to Joerg (and I’m sure Steve and Fab as well) I have a name for it.

Hackers - Heroes of the Computer Revolution

If you are still looking for a Christmas present for the nerd in your life, this would be a good one.

Siliconned

I picked up this book recently after listening to an interview on the Tech Won't Save Us podcast (kudos to John Medland for putting me onto that). It's a really great read and very eye-opening. After reading the book, a lot of business decisions that I

Advent Of Code 2024

Advent of Code is a great opportunity for practice. What are you practicing this year?

Sign up for more like this.