3 ms·

I have a "lab book", but I stopped writing into it. It mostly contains information i gathered about a particular section of the code base or how a solution migh

I have a "lab book", but I stopped writing into it. It mostly contains information i gathered about a particular section of the code base or how a solution might work or what I learned about our business domain. But over time the constant context switching of topics I had to work on made me stop it. I would like to revive it. However, i want the information in there (the lessons learned this week) to be less project/issue specific, but more transcending and transferable to new problems/environments. Do you have a set of questions you pose yourself whose answers guide the write-up and make it a worthwhile knowledge vault? === Not sure if I expressed myself in a coherent way.

mtlynch 7y ago
Oh, that's interesting. I do some introspection when I'm writing my weekly updates[1], but not to the depth that you're describing. But What Got Done should work as a lab book, although I haven't implemented search yet, and it sounds like that might be important to you. The time when I do deeper reflection is when I write my monthly retrospectives. [2] I don't have a standard set of questions that I ask myself, but that's a good idea. My method so far has been to state what lessons I learned, evaluate how I did against my goals for the month, and define goals for the subsequent month. [1] http://whatgotdone.com/michael http://whatgotdone.com/michael [2] https://mtlynch.io/retrospectives/ https://mtlynch.io/retrospectives/