Sort of. Since all I think about in my waking hours is product, company, roadmap, and vision, my notes are very specific to these issues and goals and simply have become the company's knowledge base.

The notes for the talks are practically non existent and are just a subset, and a few lines at most.. Other notes are about strategy, handbook to be able to operate the company from paying taxes to hiring, onboarding, and firing to how to write issues and commit messages, to tools we use or could use, to features and roadmap, to the experience from soup to nuts of different stakeholders, to the induced demand and workers influx it hopefully will cause, to what the company should focus on for the next two months to become what it will in the next five to ten years with nth order effects. Different x maginification from the bug fix to the economic consequences on countries with poor connectivity, and how closing an issue relating to compressing static files moves us a hair.

Success is the team not missing a beat if I disappear, because everything would be in place for continuity and growth and slashing cumulative lifetimes of suck.

I've always had a proclivity for writing, but there are other reasons I'm doing it that much and want to do it more. Some hard transitions and developments that almost killed the company, and we turned it around with some hard learned lessons and the earned "wisdom" not to have it happen again.