Notes from the work.
Occasional writing on the problems we keep meeting: measurement that breaks without telling anyone, infrastructure decisions disguised as line items, and the gap between a fix being correct and a fix being live.
Writing
Published when there is something worth saying.
-
When the measurement chain breaks, the money goes first and the dashboard goes last
A tracking fault does not announce itself. The chart keeps drawing a line — it is just the wrong line, and every decision made on it is wrong too.
-
One tenant, one boundary: shared hosting is an architecture decision
If fifty sites share one operating system user, you do not have fifty sites. You have one site with fifty front doors.
-
The fix worked. The cache disagreed.
A change that is correct on the origin and invisible to customers is one of the most reliable ways to waste a week.
Next step
Prefer a conversation to a reading list?
Most of what is written here started as a client problem. If one of them sounds like yours, say so.