I was at one place where I kept a public blog about day to day stuff. I mean 'public' in the sense that it was internal, but I shared it with the team. Meetin

I was at one place where I kept a public blog about day to day stuff. I mean 'public' in the sense that it was internal, but I shared it with the team. Meeting notes, any issues I hit, resolutions, etc. It wasn't necessarily something I posted to every single day, but at least weekly. Ended up being around 2-3x/week. Notes on why certain decisions were made, other options tried, etc. I had originally put some of this in comments, but was working some place where "comments in code are bad - remove them all - should be self-documenting" so... I needed to put them someplace. I was lightly teased for keeping this log. Then I quit, and a couple folks told me they were still looking up things in my blog months after I left, as they couldn't tell why certain things were done. "Couldn't use X because person Y indicated we weren't paying for X, so I had to build a smaller Z version instead" - that type of thing. It 'helped' some because we got a new dept manager in, say, June, and July was the time for all the 'end of fiscal year' review stuff. Dept manager had to do 10-12 staff reviews in... 3 weeks? He had no ability to contextualize most of anything, but I had a running history of months of issues, resolutions, meeting notes, conversations, and more. I will say that was... over a decade ago, and I don't think I've been that diligent since. It was useful, but definitely more work than I would feel comfortable committing to again, at least with current workloads. The workload there was surprisingly... light enough such that I could keep docs as a regular part of week to week work.