Visibility, Narrative, and the Quadrant Trap

Convert visibility from an aesthetic objection into an explicit political instrument. Build a sustainable narrative practice — the quarterly self-authored document, a public-writing rhythm sized to your temperament — and a clear-eyed reading of which visibility-leverage quadrant your current work portfolio sits in. Visibility is logging. The application that doesn't log doesn't fail less; it fails invisibly, and when something breaks nobody can diagnose it, and when something works nobody can replicate it. Engineers who refuse visibility are operating their careers without logs. The quadrant matrix maps onto observability: Q1 is the well-instrumented service doing real load with dashboards that show it; Q2 is the over-logged shim — lots of metrics, no work; Q3 is the unlogged service quietly handling the most-trafficked endpoint, which gets blamed whenever anything else breaks precisely because it has no observability; Q4 is the abandoned service consuming compute for reasons no one remembers. The engineer who refuses to write the quarterly document because it feels like "marketing themselves" is the engineer refusing to add logging because it feels like "marketing the service." The refusal doesn't preserve purity; it guarantees that when the work is questioned — and it will be — there is no record from which to answer.