HomeWriting

Writing

Field notes on technical environments, delivery drag, ownership gaps, and the hidden constraints that make systems harder to change.

Stability · 6 min
Why messy technical environments become unpredictable
Unpredictability tracks weak boundaries and unclear ownership more often than it tracks lack of effort.
Read note →
Bottlenecks · 6 min
Why busy teams stop making progress
Utilization is not throughput. When the constraint stays invisible, teams stay busy and still stall.
Read note →
Bottlenecks · 7 min
How to find the real constraint in a software team
Follow symptoms upstream until one lever explains the drag. Then test that lever with a small, safe experiment.
Read note →
Architecture · 6 min
Why technical debt is usually ownership debt
Code is the receipt. The debt is fuzzy ownership, unclear trade-offs, and risk postponed past the point where it stays cheap.
Read note →
Stability · 7 min
What stable, predictable, and boring systems actually require
Predictable delivery tracks explicit ownership, tight feedback on critical paths, and constraints people can reason about before ship.
Read note →

If something here sounds familiar, tell me what's unstable.