System Architecture

Software architecture principles like low coupling, high cohesion, and minimal side effects matter more than ever when AI agents are the ones navigating your codebase.

Exploring software architecture that returns data to users and enables collaboration in every tool.

Note for numberphiles: all numbers have been rounded to their first significant digit, because I’m a fan of Rob Eastaway’s “zequals” method of getting to the point when it comes to estimation. It’s much more valuable to walk away with the heuristic “some dude got a 300x memory reduction by swapping out a database he hacked together for a tiny, static, specialized data structure that does exactly what he needs it to and no more.”

Idempotency is not just an HTTP header or a key lookup. This article covers the failure cases that bite real APIs: different requests with the same key, concurrent retries, partial success, downstream uncertainty, response replay, expiry, and duplicate message handling.

Learn how Beaver triples let MPC protocols multiply secret shares without revealing private inputs, using a simple group dinner example.

Opening a contemporary app during a major final, you engage in a moment of controlled chaos, where thousands of bets flood the system every second. Therefore, what feels smooth to you is actually a high-speed balancing act. Traffic spikes rise sharply during key plays, so millions react at once as emotions drive rapid decisions, with

Saish Sali, Nipun Kumar, Sura Elamurugu

By: Brett Axler, Casper Choffat, and Alo Lowry

Orchestrating Media Workflows Through Strategic Collaboration

The Internet is almost anonymous and privacy-preserving by design. I mean, unless some administrator actively tries to track you, there is no built-in...

Reading a book about bowling is not the same as actually bowling. If that resonates with you and you want to learn more about large language models, check out the LLM From Scratch project. The hand…

Distributed tracing explained with concrete debugging scenarios: slow requests, deploy regressions, environment errors, user-specific bugs, and cache misses.

Announcing AccountQueues: per-user, per-key queue isolation, provider flow control headers, and why 2 RPS default protects the internet.

What happens when you stop managing retries and start shipping features. Scale requests, not pods.

EZThrottle is a multi-region HTTP proxy for external APIs. Race requests across regions, survive partial outages automatically.

Move the layout decision out of the clients and into the API. One JSON contract; every client renders it in its own programming language or framework.

The internet you grew up on isn't dying. A commercial veneer glued on top of it is.

Build caching is becoming an everyone problem. Here is how we think about productizing it at Tuist for indie developers and small teams, not just enterprises.

Working Backwards PR/FAQ Instructions & Template Working Backwards PR/FAQ Instructions & Template Start with the customer and work backwards—harder than it sounds but a clear path to innovating and delighting customers—a useful working backwards tool: writing the press release and FAQ before you build the product. Introduction Most of Amazon’s major products and initiatives since […]

You should too

An interactive exploration of how GPS works — from the speed of light and trilateration to the cheap clock problem and Einstein's relativity corrections.

A deeper dive into why shell scripts cannot replace a proper CI control plane, drawn from years of building and operating CI systems at scale.

Durable queues, streams, pub/sub, and time-trigger scheduling on SQLite. One file, zero servers.

Learn how Linux containers are built from the ground up. Starting with the mount namespace and a root filesystem, see why PID, cgroup, UTS, and network namespaces naturally follow - and how this foundation makes concepts like bind mounts, volumes, and persistence in Docker or Kubernetes much easier to grasp.