Parallelized and cached the build; PR feedback that used to take the afternoon now lands in minutes.
See the full storyProof of work
Capacity planning was a spreadsheet nobody believed, and we kept finding the ceiling the hard way — in production, during the biggest week of the year. I made headroom measurable: load-tested against real traffic shapes, found the true limits, and gave us the numbers to scale before the wall instead of into it.
Parallelized and cached the build; PR feedback that used to take the afternoon now lands in minutes.
Costs were climbing faster than usage and nobody owned the number, so every team assumed someone else was watching it. I took the problem, instrumented spend down to the service level, and worked through the biggest offenders one at a time until the trend line bent and stayed bent.
Replayed the write-ahead log and reconciled balances; zero customer-visible discrepancies.
The system was buckling under growth and the old design had run out of room — every fix bought weeks rather than quarters, and the next step up in traffic would have broken it outright. I owned the redesign end to end: the tradeoffs, the migration path, and a rollout that kept old and new live until the cutover was boring.
Moved data and traffic closer to users; cross-region tail latency fell 45% with no consistency regressions.
Make the right thing the easy thing for every engineer I work with.
In public
Practical bits
Unlock with a company account to message directly and reveal:
Jump back to the board with this background already filtered in.
