Similarly I tend to overdocument everything, everywhere: emails with summaries from in-person chats; messages confirming something decided/agreed upon during a

Similarly I tend to overdocument everything, everywhere: emails with summaries from in-person chats; messages confirming something decided/agreed upon during a meeting; commit messages with details about why and how something non-obvious was decided and implemented; code comments linking to documents when some product decision was made that I objected to; comments on tickets about decisions/discussions; PR descriptions referencing documents related to the task. It's not only to cover my ass but also to leave as many breadcrumbs in the trail to anyone that needs to read this in the future to understand what happened (including, most times, myself). It's saved my ass many times and it's just a natural part of my workflow.