This advice reminded me of blogging at work, something that I started doing a few years ago and encourage others to do. I used to blog just to share nitty-gritty technical details of what I was up to, and coworkers found it interesting enough to read and learn from, and soon others started blogging. But then I realized there were benefits I didn't anticipate. For example, looking back over my last 8 posts or so, I found times where I was particularly productive and times when I wasn't. Sometimes I wasn't productive because I needed to learn new things, but other times it was because I was stuck in meetings or low-value activities. With a log of what I was doing, such low-value activities stuck out to me pretty clearly and helped me prune them.

You mention CYA which blogging can also help with, depending on the granularity of your posts. Personally, I open a blog post draft each Monday and just itemize things I do in the draft, and then on Friday I flesh the post out and submit it. It's been cool reading peers' blogs, too, because some people go very technically deep--or even just link to pull requests which do the same--compared to what is tracked in a GitHub issue or Jira ticket. So it ends up being educational material for everyone with built-in CYA should you really need it.