Back to blog
Design•June 23, 2026•5 min read

What 15 ADRs taught me about building solo

Building Streetvers solo - Unity game, FastAPI backend, admin panel, hardened VPS - means no one catches your bad calls in review. So I review them later, by writing each decision down as a numbered ADR. Fifteen of them now sit in the repo.

Decisions are the artifact

An ADR records what I chose, what I rejected, and why - id-or-slug lookups, the OVR boundary, the token-version revocation scheme. Six months on, the ADR is the difference between "this looks weird, let me not touch it" and "right, I had a reason." Solo, the records are your second engineer.

The code says what the system does. The ADRs say what you were thinking - which is the part you'll forget first.

Sequence so future-you isn't blocked

Decisions also let me build in an order that keeps the solo path unblocked:

  • The API was shaped for the Unity client before that client existed, so wiring it up later doesn't reshape the backend.
  • The admin panel runs against an in-memory mock (VITE_USE_MOCK), so I can demo and screenshot the whole tool with no backend running.
  • Authoring characters in the admin doubles as the integration test the API would otherwise need.