The Backtrace
Field notes on software that holds up
Issue archive · 2026
Twice monthly · 42 issues · 12,480 readers
Essays and field notes on building software that survives contact with production — written by the people doing the work.
Get the next issue
One essay, three field notes, every other Thursday.
9 issues found
Newest first
We rebuilt our sync engine around a latency budget instead of a feature list. The result was less code, fewer meetings and a product that finally feels instant.
Ilya Petrov
Staff engineer · 5 min read
A component library is a promise about the future. Here is how we kept ours when the frontend changed underneath us.
We tested three pricing models with forty teams. The winner had less to do with revenue than with how honestly it described the product.
Four-hour shifts, a written handoff and one rule about pages after 22:00. A year later, nobody has left the rotation.
Most roadmap debates are data-shaped guesses. A small instrumentation sprint can turn an argument into a measurement.
Every toggle is a promise to maintain two paths forever. We deleted thirty-eight of them and support tickets went down.
We removed the Friday deploy freeze and added a rollback drill instead. The result: calmer releases and better sleep.
Two-way doors are not an excuse to move fast. They are a reason to write down how you will walk back through.
The first ten tickets from new accounts read like a usability test written by people with no patience left.
Showing 9 of the last 9 issues