# Productivity
All Productivity notes →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.
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.
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.
Personal Architecture Decision Records
Adapting the ADR format — context, decision, alternatives, consequences — to personal and career decisions, not just system architecture.
Debugging Efficiently
A general-purpose approach to root-causing an unfamiliar problem — narrowing scope, forming falsifiable hypotheses, and knowing when to stop digging and ask for help.
Research Workflows
The information-gathering loop underneath debugging and design work — source triage, spike time-boxing, and converting findings into a written artifact.
5 — Managing Large Learning Backlogs
Keeping a large backlog of things-to-learn from turning into background guilt — triage rules for a reading list that will never hit zero.
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.