b3126044e8
- Simplify flatten_vault API to return usize instead of MigrationResult struct - Add KEEP_FOLDERS: attachments/ and _themes/ alongside type/, config/, theme/ - Use HashSet for collision tracking in unique_filename - Update wikilinks from path-based [[folder/slug]] to title-based [[slug]] - Clean up empty directories after flattening - Flatten demo-vault-v2: move all notes from type-based subfolders to root - Update smoke tests for flat vault structure - Remove migrate_to_flat_vault from repair_vault (one-time migration only) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
4.5 KiB
aliases, Is A, Topics, Status
| aliases | Is A | Topics | Status | |||
|---|---|---|---|---|---|---|
|
Evergreen |
|
Published |
Training Load and Knowledge Work
Endurance athletes understand that adaptation happens during recovery, not during training. You get stronger by stressing the system, then allowing it to rebuild stronger. Skip recovery and you get injured or overtrained.
Knowledge work follows the same principle. Deep focus creates cognitive load — stress on your attention system. Without recovery (sleep, walks, boredom), you don't consolidate learning, and creativity degrades.
The best writers, programmers, and thinkers I know are obsessive about protecting recovery. Not because they're lazy, but because they understand the adaptation model.
In cycling, training load is quantified precisely using metrics like Training Stress Score (TSS), which combines duration and intensity into a single number. Over time, you track Chronic Training Load (fitness), Acute Training Load (fatigue), and the balance between them (form). This framework makes it possible to push hard enough to improve without pushing so hard that you break down. The numbers do not lie. When your fatigue exceeds your fitness by a certain margin, performance degrades regardless of how motivated you feel.
Knowledge work lacks equivalent metrics, which is both a measurement problem and a management problem. We have no TSS for cognitive work. A day of deep writing, a day of back-to-back meetings, and a day of debugging a complex system all deplete different cognitive resources, but we treat them as interchangeable "work" and manage them by the same crude metric: hours. The result is that most knowledge workers have no idea whether they are in a productive training zone or accumulating a fatigue debt that will surface as burnout in three months. They only discover it after the breakdown, which is like an athlete only discovering overtraining after the injury.
My attempt to apply training load principles to knowledge work has been imperfect but useful. I track three types of cognitive work — creative (writing, strategy), administrative (email, operations), and social (meetings, calls) — and try to manage the weekly balance between them. A week with 20+ hours of creative work requires less social and administrative load to stay sustainable. A week heavy with meetings requires lighter creative expectations. I also apply the 3:1 principle from cycling: three weeks of progressive load followed by one lighter week. This is not precise science, but it is dramatically better than the default approach of "work as hard as possible until something breaks."
The deeper principle connecting athletic training and knowledge work is that both are biological processes governed by the stress-adaptation cycle. Your brain, like your muscles, needs progressive overload to grow and recovery to consolidate those gains. The knowledge workers who produce the most over a career are not the ones who work the hardest in any given month. They are the ones who sustain a productive training load across years without burning out. This requires the same periodization discipline that athletes use: structured cycles of intensity and recovery, not a flat line of maximum effort.
Key insight
The stress-adaptation model from endurance training is the best available framework for managing knowledge work sustainably. The key principles translate directly: progressive overload (gradually increasing the complexity of the work you take on), periodization (cycling between intense and recovery periods), and respecting recovery as the phase where actual improvement occurs. The main barrier to applying this framework is the absence of quantitative metrics for cognitive load, which means knowledge workers must rely on self-awareness and qualitative tracking rather than the precise numbers athletes use. Imperfect tracking is vastly better than no tracking.
Related
- cycling-teaches-patience — Patience and pacing as the practical application of training load management
- recovery-week-in-training — Recovery weeks as the structural implementation of periodization in knowledge work
- sleeping-more-is-a-superpower — Sleep as the primary recovery mechanism for cognitive load
- on-founder-energy-management — Energy management as the founder-specific application of training load principles
- the-two-types-of-hard — Training load context helps distinguish genuine fatigue from resistance