2026W34
A few interesting articles I read over the past few days
- Git at any scale — The move that stuck with me is putting a write-ahead log in S3 as the source of truth and treating the local NVMe repos as a warm cache you can throw away. That flips the usual problem, once the storage layer enforces consistency you no longer need the coordination layer to be reliable, so they can replicate with lossy UDP gossip and just verify against S3 on read. GitHub’s Spokes is the useful contrast, its three-phase commit binds every push to the slowest replica and forces you to treat repos as pets whose exact location you track. The numbers that make it concrete are 120 pushes/second on S3 Standard and linear read scaling past 100 replicas, which is the payoff for pushing correctness down into storage instead of up into a consensus dance.
- What is a Harness? | EARENDIL — I’ve been using the word “harness” for months without a clean definition, so the breakdown into system prompt, tools, agentic loop, and translation layer was worth having spelled out. The climbing metaphor earns its place because a harness supports you without taking control, which is exactly the distinction between the harness and the model doing the deciding. The part I keep turning over is the translation layer, since being able to swap Anthropic for OpenAI or an open-weight model is what actually shifts leverage from the AI companies to whoever runs the harness. Framing the harness as the thing you own and run locally, rather than a proprietary app you rent, is a cleaner argument for local agents than the usual privacy pitch.
- How I Find Problems to Solve as a Staff Engineer — The advice I expected was “block time to think strategically” and instead he argues the opposite, act like a sponge, absorb problems as they pass by, and let them pile up until a shape emerges. Deliberately not acting on every request is the counterintuitive bit, because waiting is what tells you whether a problem is real, the ones that matter resurface on their own. His Perfetto example lands the point, a stack of specific UI requests collapsed into a single need for personalization, which is a much better thing to build than any one of the features asked for. The warning I want to keep is that a common shape is only a hypothesis and elegance is not evidence, since I know how tempting it is to fall for a clean abstraction before anyone has confirmed the pain is shared.