Keep an Error Journal

Yesterday I listened to the excellent episode Bugs considered harmful of Scott Hanselmans podcast hanselminutes. (If you’re not subscribed to the podcast, stop reading here and subscribe.) Scott talked to Douglas Crockford about the history of computer science, about our understanding of the history and the missing self-consciousness about predecessors and principles of computers and programming languages.

That in itself makes an interesting podcast, but then the topic came to bugs and how to learn from them. Douglas Crockford mentioned an error journal that a software developer should write all bugs into, as a reference and as an excercise. The famous example of this is Donald E. Knuth and his document The errors of TeX. I’m still searching for the article mentioned in the podcast, where Donald Knuth described the usefulness of his error journal. Unfortunately the hanselminutes podcast does not have show notes, so there is no direct link to this article… :-(

Anyway, I decided to start my own error journal today, after a colleague discovered a very silly bug that I created by manually copying data from one database to another. I couldn’t even remember doing that, but fortunately I created a ticket in JIRA before doing the actual task, so we could rule out a misbehavior of the database and pin the bug down to my human error. Maybe the error journal helps me to prevent such bugs in the future, and I do hope that simply writing it down will help me to remember this in the future.

Do you keep an error journal or something like that? Or do you have another way of remembering the types of bugs that you found, created or fixed?

Weitere Artikel

Crossfit Open WOD 17.5

Crossfit Open WOD 17.4

Crossfit Open WOD 17.3

Crossfit Open Workout 17.2

Crossfit Open Workout 17.1

Run Feedbin in your local Kubernetes cluster

Running Threema Web in Docker

Neues Workout Video

Diät Update #1

Workout 21.01.2017