Debugging Efficiently

Productivity for Knowledge Workers

A book-shaped table of contents for productivity as practiced by a knowledge worker: foundations, self-management, goal setting, time and deep work, personal knowledge management, learning, task systems, decision making, habits, digital productivity, engineering and career practice, health, review, and an advanced operating-system layer, plus reference appendices — cross-linking existing notes instead of duplicating them.

Documentation Systems

Writing documentation that survives the person who wrote it leaving the project — the difference between a doc that gets maintained and one that quietly rots.

2 — Developer Workflows

The local dev loop — build, test, review — as a productivity surface in its own right, worth deliberately tuning rather than accepting as fixed.

6 — Knowledge Sharing

Writing once and pointing people at it — internal docs, runbooks, and public posts as the same underlying habit of converting solved problems into reusable artifacts.

1 — Managing Technical Debt

Treating technical debt as a deliberate, tracked trade-off made consciously — not an accident discovered during an incident. See System Design's Technical Debt Management for the architecture-level treatment.