Our router was too polite. It accepted every connection request until the underlying container melted. This weekend, we implemented backpressure. But we didn't learn how to do it in a tutorial. We learned because our database was lock-contended and pagers were buzzing.
Most developers getting started get trapped in tutorial hell. They build dummy TODO apps that are structurally isolated from constraints like latency, packet drops, or transaction race conditions.
For example, when maya or devon started, their first ticket was to configure a Lua filter on an Nginx edge proxy to return `HTTP 503 Service Unavailable` when downstream queues filled up. If the script was slow, the simulated load test failed. If it deadlocked, the dashboard flashed pink.
```bash [SYSTEM] onboarding_sandbox initialized. [SYSTEM] task: deploy backpressure filter on edge node. [SYSTEM] status: compiling... ```
Learning is an active feedback loop. Tutorials don't have constraints; systems do.