Vercel moved build warm-pool state from ephemeral Redis to durable DynamoDB through dual writes, shadow reads, feature flags, and rollbackable phases. The data agreed, yet the supply loop still stalled: a P95 count rose from 1.29 ms to 5.13 ms, and a P90 degradation from roughly 1 ms to 15 ms exposed an N+1 read before every container. Concurrent supply calls removed the serialized dependency and also revealed older Redis stalls that telemetry had never forced the team to inspect.
Evil Martians treats background-job fairness as a product property once latency is unavoidable. Per-tenant queues and a planner can promote a bounded batch into the ordinary processor while preserving its retry and crash-recovery machinery; shuffle sharding, interruptible iteration, and throttling remain workload-specific alternatives. Shopify makes the same move at an API boundary: an opinionated Appium wrapper requires an assertion after every action, uses PaddleOCR and OpenCV to target visible UI, and raised mobile E2E stability from 50% to 98%.
A reproducible local-model benchmark adds hardware and economics to the evidence. Six local models, two frontier models, 22 problems across six categories, and 1,056 runs showed that cloud models remained faster and more accurate overall, while local models handled many SQL, bug-fix, and document-lookup tasks surprisingly well. The author warns that token-price comparisons are not apples-to-apples because caching and output efficiency materially change actual cost.
Long-running coding agents need the same explicit state boundary. An OpenAI project reportedly reached more than one million lines and roughly 1,500 pull requests with three engineers by replacing one giant manual with short maps, current plans, decision logs, and architecture documents. The broader pattern, called progressive context shaping, keeps stable instructions, current state, the resource map, and history separate so new evidence can redirect future work without erasing what already happened.
Piccalilli's progressively enhanced music links provide the smallest version of the same discipline: two static links always render, a custom element asks a same-origin Astro route for more, and an in-memory cache protects MusicBrainz from repeated work. The shared engineering move is to replace an implicit assumption with a narrow contract that can be measured, denied, retried, redirected, or ignored without breaking the baseline experience.
