01 / Featured engineering story
SeatLedger Deployed demo
One seat left.
Two people booking.
A reservation system I built to explore competing requests, expiring holds, and safe retries. Try the product or follow the engineering decisions.
Synthetic shared accounts · Free backend may take a minute or more to wake · No personal information
Actual product capture - 01 / Protect capacity
Serialize reservation changes at the event.
- 02 / Handle retries
Persist idempotent outcomes with lifecycle changes.
- 03 / Explain the numbers
Build replayable analytics apart from live inventory.
Verification and demo limitations
18 October 2026 · Deployed portfolio demo · CI: 265 backend, 56 analytics and 28 browser tests passed, zero failures/errors/skips. Synthetic evidence, not production load or real-user validation.
Synthetic shared accounts and events; do not enter personal information. Free backend may sleep, hosted email is disabled, and analytics refresh is manual. Existing hosted events were reported past; booking may be closed. No real-user production launch.
Inspect verification scope


