Dreams are data. Six years of sleep journaling.
A more personal entry. Six years of dream notes. What it did for me as an engineer: trained an attention nobody asked me to train.
// body
I keep a notebook for dreams. I have done it, with one long lapse, for about six years. The notebook lives on the nightstand. The rule is simple: before any phone, before standing up, before water, I write whatever I remember. Some mornings the page stays blank. Some mornings I lose the next half hour.
I am not interested in the symbolism. I'm not pulling a Jung book off the shelf. The reason this matters at all to a software-engineering blog is sideways.
What journaling dreams trained
It trained attention to detail that no one ever asked me to pay attention to.
Dreams degrade fast. Within ten minutes of waking, half the content is gone. Within thirty, most of it. To capture them you have to fix the texture before the structure: a colour, a sound, the feeling of a corridor, the wrong-ness of someone's face. Then, working outward from those anchors, you reconstruct what happened.
That happens to be a great drill for debugging.
How it transfers
Debugging hard bugs has the same shape. The bug is the dream — it leaves traces that fade as soon as the system reboots. The fix is rarely a single line; it's "I noticed this small wrongness at the edge of a log line at 2am, and that small wrongness led me to a misconfigured cache, which led me to the actual cause two hops away."
The skill is noticing what doesn't quite fit. Any practice of observation builds that skill in any other domain that demands it.
Any discipline of observation makes you better at any other discipline of observation.
This is not a productivity post. I'm not telling you to journal at 6am. I am saying: the engineer-version of you is built by every habit that demands close attention, even — maybe especially — the ones that look unrelated.