One software engineer’s core practice—using a physical engineering notebook—has proven vital for productivity and clarity. In a recent Mastodon poll, 25% of respondents admitted to using one, while 40% said they didn’t, and 34% were unfamiliar with the concept. This reveals a gap in adoption, suggesting the practice isn’t just a niche habit but a potential game-changer for developers.

An engineering notebook isn’t a specific product but a method of documenting work in real time. Key traits include detailed records of tasks, dated entries, and append-only notes that avoid edits. This approach ensures clarity and replicability, as future you (or others) can trace the thought process behind decisions. The author emphasizes that the level of detail matters most, as notes must be useful even to someone else—future self included.

The author, who started using the practice in 2016 during consulting work, credits it with improving memory and decision-making. Handwriting, in particular, aids retention, a benefit supported by studies on cognitive engagement. While the notebook isn’t used for reviewing past work beyond daily check-ins, it’s a critical tool for thinking through problems. The author notes that the act of writing forces deeper understanding, especially when planning code changes before typing them.

For those considering it, experimentation is key. The author’s left-handedness and preference for e-ink devices highlight how personal needs shape the practice. Though not universally adopted, the author urges developers to test the method, share findings, and refine it. As the author concludes, this practice isn’t just about organization—it’s about fostering clarity and intentionality in software development.