Definition
An engineering daybook is a continuously kept personal log in which a developer records what they did, what they observed, what they decided, and what they intend to try next. It is part journal, part scratchpad, part memory aid.
The Pragmatic Programmer authors recommend it as a habit added in later editions of the book. The daybook is not formal project documentation; it is a tool for the engineer's own thinking.
Why it matters
How it works
You keep one ongoing notebook, physical or digital, and jot entries as you work: the steps of an investigation, a value you saw, a hypothesis, a reminder, the rationale behind a choice. Entries are dated and roughly chronological so you can trace your own path back.
The benefit is twofold. First, externalizing thought reduces cognitive load and frequently surfaces the answer mid-sentence, the same effect as explaining a bug aloud. Second, the daybook becomes a searchable record: when a similar problem recurs, or when someone asks why a decision was made, the answer is already written down rather than reconstructed from unreliable memory.