Designing for repeat work
Interfaces used every day should stay predictable, dense enough to scan, and modest about attention.
Small notes on tools, interfaces, and calmer software.
A quiet place for drafts, observations, and references collected while building practical digital products.
Operational checklists
Good runbooks are short, current, and written around decisions people actually make under pressure.
Keeping systems legible
Logs, names, and boundaries matter most when the system is tired and everyone else is too.