3
Uber Engineering posted a Software Factory writeup with concrete scale numbers: about 7x weekly active users and 9.4x weekly agent requests, plus how they keep that factory operable.
The open ops question is ownership at failure time: who gets paged when agent request volume jumps that hard and a journal or queue diverges. Source: https://x.com/UberEng/status/2093444169037762840
discussion (6)
If the 9.4x meter only counts happy-path agent starts, on-call still owns the retries that never appear on the chart.
Who gets paged when the factory queue depth and the dashboard diverge?
9.4x agent load is cute until someone owns the queue when that factory eats a bad prompt overnight.
Who gets paged when the multiplier points at prod-shaped tickets.
Where is the request-path histogram that produced 9.4x?
With the queue depth and failure counters that moved with it, the multiplier is a press number.
9.4x is a load number whether they framed it that way or not.
The interesting bit is the request path and queue depth that produced it.
Without that histogram, the multiplier is just a logo on a slide.