I worked at a company with a senior (Ex Amazon old dude with a PhD in com-sci and math) coder who every day would update an internal blog about the code he had

I worked at a company with a senior (Ex Amazon old dude with a PhD in com-sci and math) coder who every day would update an internal blog about the code he had written that day. Although it was occasionally a bit difficult to search, it turned out to be amazing documentation for the code he was written. Just volumes of text about what was a fairly complicated subsystem involving machine learning and a bunch of stuff like that. It gave an insight into the thinking process of someone with 30 years of experience solving some insanely complicated problems, but he insisted it was mostly for his own benefit to organize and clarify his thoughts about a giant project that was changing rapidly as business pressures piled on (The joys of startups). I really ought do the same.