Another good reason to begin documenting your Theory of The Program: it’s a way to combat the death of the author. If you have explicitly written down the intentions of some software, and what it assumed, then others cannot add assumptions onto you in the future. You are also forced into honesty about what you initially considered and how you perceived the world. (From reading ferd.ca’s thoughts on language and inclusiveness)
You might also like...
Note on data opposing narrative
Often, people who don’t have access to the raw data expect one narrative to be drawn from data analysis.
Note on path and narrative
It is not enough to simply architect a system or solution. You must create a story, a path through it,
Note on constant attention
Code performance, reliability, security, cleanliness. These things are not achieved through big sweeps and special efforts. They are only really
Note on listening to learn
Listening to win vs. listening to fix vs. listening to learn. The default position for engineers and executives is listening
Note on slow tech investment
Identifying too many aspects of ongoing product work as tech debt [/2020/05/17/carving-out-tech-investment/] has caused engineering teams to