4 ms·

> Counterpoint: when the product manager attempts to revise history about what was specified for a certain feature at a certain point in time, I'm often able to

> Counterpoint: when the product manager attempts to revise history about what was specified for a certain feature at a certain point in time, I'm often able to search my emails for a copy Hit the nail on the head. I even send emails summarizing hallway conversations I've had, just so there's a record of what understanding I came out of the conversation with. In part because ephemeral conversations (be they in person or over some IM system) often leads to misunderstanding and a summary can surface those misunderstandings, and in part to cover my ass when someone revised history.

piva00 1y ago
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.