Observations on Sleep and Energy | Generated by AI
Question: I’ve noticed three things about my own sleep and energy management: (1) mental fatigue and physical fatigue are different — yesterday my brain was tired and I had a headache, but my body wasn’t tired, so I went out for dinner with a friend nearby and the headache was gone within half an hour; (2) I still cook on weekdays, which keeps my hands and body moving as light exercise; (3) 6–7 hours of sleep looks short, but after a full busy day, my sleep is fairly deep. Does this hold up?
Answer:
Your three observations map well onto actual physiology, and you’ve essentially reverse-engineered some real mechanisms by paying attention to your own body.
On mental vs. physical fatigue: these really are distinct systems. Cognitive fatigue is largely about the brain — sustained focus depletes attention-regulating circuits (prefrontal cortex), builds up metabolic byproducts like adenosine locally, and tension-type headaches often come from prolonged static posture, eye strain, and shallow breathing at a desk rather than from any muscular exhaustion. Your fix worked through several channels at once: walking increases cerebral blood flow, leaving the screen releases eye and neck muscle tension, social conversation engages completely different neural circuits (which is genuine “rest” for the depleted ones), and eating stabilizes blood glucose. A 30-minute recovery is exactly what you’d expect from a tension headache, not a sign of anything systemic. The general principle you’ve found is real: the cure for mental fatigue is usually different stimulation, not lying down. Rest is not the absence of activity — it’s switching the load to an idle subsystem.
On weekday cooking: this is what researchers call NEAT (non-exercise activity thermogenesis) — the standing, chopping, walking around the kitchen. For someone with a terminal-first, desk-heavy workflow, these scattered 30–60 minute blocks of light movement matter more than they look. They break up sitting time, which independently predicts health outcomes even in people who formally exercise. There’s also a cognitive angle: cooking is a low-stakes, hands-on, sequential task — closer to a moving meditation than to work — so it doubles as the “different circuit” recovery from point one.
On 6–7 hours of deep sleep: sleep quality is driven by sleep pressure (adenosine accumulation from being awake and active) and how efficiently you cycle through deep slow-wave sleep, which is front-loaded in the night. A genuinely full day builds high sleep pressure, so you fall asleep fast and spend a larger fraction of the night in deep stages — higher sleep efficiency. That said, one honest caveat: feeling fine on 6–7 hours is common, but chronic mild sleep restriction is notorious for being subjectively invisible while still measurable in attention and learning tasks. The cheap test is whether you wake naturally without an alarm on free days at roughly the same duration. If yes, 6–7 hours may genuinely be your number. If you sleep 8.5+ when nothing wakes you, you’re carrying debt during the week.
The meta-skill across all three is the same one that makes you good at debugging: observe the actual system behavior instead of applying generic rules. “Tired” is an underspecified error message — you’ve learned to read the stack trace.