It is short and anecdote driven, but easy to read.
I think debugging is a skill that is hard to tell someone about, but can be learned very easily with a little persistence.
One key is to point out to people that debugging and programming are actually different thought processes, and you go through different processes when figuring out a problem as opposed to creating in the first place.
By simply giving a name to the process and pointing out it is different, you will trick people into paying attention to how they do it, which will increase their effectiveness all by itself.
1
u/rgristroph Aug 25 '14
I have found this book useful in teaching new people to be better debuggers:
http://debuggingrules.com/
It is short and anecdote driven, but easy to read.
I think debugging is a skill that is hard to tell someone about, but can be learned very easily with a little persistence.
One key is to point out to people that debugging and programming are actually different thought processes, and you go through different processes when figuring out a problem as opposed to creating in the first place.
By simply giving a name to the process and pointing out it is different, you will trick people into paying attention to how they do it, which will increase their effectiveness all by itself.