2 — Developer Workflows
Purpose
[stub: developer-workflows-and-technical-debt]
Metadata
| Author | Amit Singh |
| Scope | productivity |
Local graph
Related notes
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.
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.
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.