In regards to the review part:
What helps me is keeping around my TODO.txt month by month, as well as a lot of screenshots and images of the things I find relevant for sharing in stand ups and meetings and such (as well as presentations).
So if I need to review the past month/year (e.g. when I want to update CV/site or catch up with management), it’s just a matter of going through a bunch of text and images without a lot of unnecessary fluff, like digging through Jira. Maybe if I want to get the approximate time/effort spent on particular stuff, based on the amount of activity there.
Alongside that, it’s also nice to document stuff that was particularly good, or all the ways software broke in (and what broke how often), as well as stuff that pissed me off and made me want to quit (sometimes people/mindsets, sometimes tangible code or practices).
When the default is just going with the flow and not documenting anything and doing no self reflection, every improvement upon that helps.
What helps me is keeping around my TODO.txt month by month, as well as a lot of screenshots and images of the things I find relevant for sharing in stand ups and meetings and such (as well as presentations).
So if I need to review the past month/year (e.g. when I want to update CV/site or catch up with management), it’s just a matter of going through a bunch of text and images without a lot of unnecessary fluff, like digging through Jira. Maybe if I want to get the approximate time/effort spent on particular stuff, based on the amount of activity there.
Alongside that, it’s also nice to document stuff that was particularly good, or all the ways software broke in (and what broke how often), as well as stuff that pissed me off and made me want to quit (sometimes people/mindsets, sometimes tangible code or practices).
When the default is just going with the flow and not documenting anything and doing no self reflection, every improvement upon that helps.