4 ms·

Great advice! It is similar to something I have been doing for close to 20 years now: whenever I come across a really tricky bug of some kind (usually one that

Great advice! It is similar to something I have been doing for close to 20 years now: whenever I come across a really tricky bug of some kind (usually one that got all the way into production without being caught), I write down some notes on it. What the problem was, what we did to find it, and what we did to fix it. Most inportant is the "Lessons" part (a few sentences) - what should be done to avoid these kinds of problems in the future. I've written about what this looks like: https://henrikwarne.com/2016/04/28/learning-from-your-bugs/ https://henrikwarne.com/2016/04/28/learning-from-your-bugs/ and I have also written about general lessons extracted from all these notes: https://henrikwarne.com/2016/06/16/18-lessons-from-13-years-of-tricky-bugs/ https://henrikwarne.com/2016/06/16/18-lessons-from-13-years-...

quercusa 5y ago
The per-bug write-ups seem really useful. Have you used them for internal training or just for your own reference?
- milkytron 5y ago
  I've done the same thing, but for more than just bugs. Pretty much any time I learn something while working that I think might be easy to overlook in the future, I write it down. Some of my findings end up in internal training if it's something the team needs to know. If it's something for me, I'll just keep it in my own notes for the next time I encounter it until it's burned into my memory.
- henrik_w 5y ago
  It is mostly for my own reference. However, almost every time I come across a bug like this, I will be discussing it with people in the team. It's often hard to keep quite about it: "You wont believe what just happened..." kind of a thing.
recroad 5y ago
Good retrospectives are the key. Using cause-effect diagrams and techniques like “story of a story” help facilitate good discussion. 5 Whys as well. I try to get teams I work on to retro on all defects that escape to production.

quercusa 5y ago

The per-bug write-ups seem really useful. Have you used them for internal training or just for your own reference?

milkytron 5y ago
I've done the same thing, but for more than just bugs. Pretty much any time I learn something while working that I think might be easy to overlook in the future, I write it down. Some of my findings end up in internal training if it's something the team needs to know. If it's something for me, I'll just keep it in my own notes for the next time I encounter it until it's burned into my memory.
henrik_w 5y ago
It is mostly for my own reference. However, almost every time I come across a bug like this, I will be discussing it with people in the team. It's often hard to keep quite about it: "You wont believe what just happened..." kind of a thing.

recroad 5y ago

Good retrospectives are the key. Using cause-effect diagrams and techniques like “story of a story” help facilitate good discussion. 5 Whys as well. I try to get teams I work on to retro on all defects that escape to production.