4 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The article discusses the value of keeping a physical engineering notebook for software work. It emphasizes detailed, real-time documentation that aids memory and clarity in problem-solving. The author encourages experimentation with this practice to find what works best for individual workflows.
If you do, here's more
The author emphasizes the value of using a physical engineering notebook in software engineering. Despite polling followers and finding that only 25% use one, the author believes this practice enhances productivity and clarity. An engineering notebook isn't just any notebook; it involves detailed, real-time documentation of projects, including hypotheses, goals, and dated entries that create a permanent record. This approach mirrors practices used by researchers and is designed to be thorough enough that someone else could replicate the work based on the notes.
The author started using an engineering notebook in 2016 while consulting multiple clients, finding it essential for organization and memory. Writing by hand not only aids memory retention but also fosters deeper thinking about the work at hand. The author uses the notebook primarily as a tool for thought rather than for later review, often jotting down ideas before implementing code changes. While the notebook is a personal tool, the author encourages experimentation with formats and levels of detail, suggesting that even those who haven't tried it should give it a shot.
Questions about this article
No questions yet.