Build Notes
Ongoing notes on how League Night is being built — the decisions, tradeoffs, mistakes, and constraints that don’t usually make it into polished product updates.
New here? Start with Why League Night exists . Prefer RSS? Subscribe via RSS .
December 17, 2025
Building software for directors, not spectators
Why League Night optimizes for the person running the night, not the audience.
December 16, 2025
Why League Night tracks intent, not just results
Modeling decisions and context instead of only final outcomes.
December 14, 2025
Designing League Night for real-world chaos
Why league software has to assume things will go wrong - and design around it.
December 12, 2025
Why League Night sits between other tools
Filling the administrative gap without replacing everything.
December 10, 2025
Designing for late arrivals and imperfect turnout
Why rigid workflows fail real league nights.
December 8, 2025
Payouts are harder than they look
Why payout logic breaks naive software and how League Night approaches it.
December 5, 2025
Why we're not building player accounts (yet)
Reducing friction by focusing on directors, not logins.
December 2, 2025
Why League Night is offline-first
Designing league software around real-world course conditions, not ideal ones.
December 1, 2025
Why League Night exists
The problem this project is trying to solve - and why existing tools don't.