Independent engineering journal

Subway Voices

Field notes on software systems, useful interfaces, and the quiet work of keeping technology reliable.

Read the latest notes

Recent notes

Ideas that survive contact with production.

Short, practical observations for people who design, build, and maintain software. No feeds to chase and no account required.

Systems

Designing graceful failure into small services

Reliability rarely begins with more infrastructure. It starts with explicit timeouts, bounded retries, useful health checks, and a clear answer to what happens when a dependency is slow.

request.timeout = 3s retry.limit = 2 retry.backoff = jitter
Interfaces

Operational screens should answer one question first

A useful dashboard begins with the decision its reader needs to make. Metrics, color, and density follow from that decision rather than competing for attention.

Practice

Runbooks are executable memory

The best runbooks record checks in order, expected results, and a safe way back. They are most valuable when written immediately after the incident, while the surprising details are still visible.

Working principles

Observe first.Measure the system before changing it.
Prefer boring tools.Familiar parts make unusual failures easier to understand.
Document recovery.A fix is not complete until it can be repeated.