I also keep an error journal, which I call "The Library of Horrors", so when an error reocurs I can refer to.
I found this necessary because I tend to remember the "oh, this happened earlier..." but not the "... and this is the approach we followed succesfully" that should follow. The information is slotted in my brain, but not accessible unless I have some key reminder.
Also serves as a communication device between my past and future self, and between coworkers. The error-solving information tends to live transiently in your and your coworkers minds, and it is very valuable.
I haven't solved the method to properly identify-and-recalling. I simply save new information per project, per language, etc, with not much thinking. This would clearly be the next point of improvement.
Oh god that brings back memories from when I dared to propose sharing "failure stories" instead of success stories when I was in consulting. The look on people's faces was that rare blend of disdain and horror. We can't fail, how can we share failures? I mean you only learn from each other's successes right?
I found this necessary because I tend to remember the "oh, this happened earlier..." but not the "... and this is the approach we followed succesfully" that should follow. The information is slotted in my brain, but not accessible unless I have some key reminder.
Also serves as a communication device between my past and future self, and between coworkers. The error-solving information tends to live transiently in your and your coworkers minds, and it is very valuable.
I haven't solved the method to properly identify-and-recalling. I simply save new information per project, per language, etc, with not much thinking. This would clearly be the next point of improvement.