Tagged operate
4 pieces
- · 7 min read
What Happens to Your AI Feature at Ten Times the Traffic
An AI feature does not scale like the rest of your product. Its cost is per-request and does not amortise, its latency degrades in a shape most load tests never produce, and its failure mode under saturation is to return plausible garbage rather than to reject the request. All three arrive together, on the day the feature succeeds.
- · 7 min read
Reconciliation Is Not a Nice-to-Have
Prevention mechanisms fail silently. Reconciliation is the only part of a money-moving system that can tell you they did, and it is the component most often deferred, because it produces no feature and its value is invisible on every day it finds nothing.
- · 7 min read
Systems You Cannot Take Offline to Fix
Most engineering practice assumes you can stop the thing to work on it. Remove that and the entire method changes: you diagnose from passive observation, you change one variable per window, you validate in shadow before you commit, and you design every modification to be abandonable halfway through.
- · 7 min read
Your Green Dashboard Is Not Evidence
Monitoring answers whether the system is running. Evaluation answers whether it is right. Those are two different dials and almost every organisation has built only the first, which is why the honest sentence after an incident is not that monitoring failed but that nothing was ever watching the thing that broke.