Code performance, reliability, security, cleanliness. These things are not achieved through big sweeps and special efforts. They are only really possible by baking the practices into every day and each decision. You can’t focus on fixing them for a week. You need to invest in them slowly, constantly, over the life of the project. (Thoughts after reading about why NetNewsWire is fast, listening to a code audit webinar, and thinking about how we’ve done so much with 2 engineers at OfficeLuv.)
You might also like...
Note about the death of the author
Another good reason to begin documenting your Theory of The Program [https://www.joshbeckman.org/2020/07/12/on-theory-building-as-an-engineering-team/] : it’
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 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