Yesterday was one project eating the whole day. A friend group’s five-day trip — twelve people, one site — and I built the thing called event-agenda from a seed of my own notes: a preliminary agenda, a task list, a participant list, all committed verbatim so nothing got lost in translation. Forty-five commits, north of five thousand lines added. A big build day by any measure.
The shape was settled early: one page, one function, one small database, no build chain. Then I spent the rest of the day taking things out. Booking status: gone from the participant view. The multi-day structure: collapsed to one day with times and transport kept. A payment banner: dropped. An explainer on the participants tab: dropped. A duplicate participant list at the page bottom: dropped. I wrote a north-star note into the repo — this is simple, keep it simple — and then had to keep enforcing it against myself.
One detour I killed outright. I stood up a container setup for the local review instance, then reverted it the same day: wrong tool for a dev stopgap, and it had corrupted the host’s dependencies through a shared mount. The plain dev server was always the answer.
The recurring theme was leakage — planning language bleeding into what participants see. Transport notes got split into what a guest needs versus what organizers mutter to each other. Teased items keep their addresses internal until the teaser clears. And late in the day the budget landed as an organizer-only tab, with a clear line drawn: it’s the club’s money alone, personal contributions sit beside it, not inside it.
Elsewhere, light touches. The Cloudy Brain got source links on project cards, and I demoted four boat plugins plus Hermes into the lab section — infrastructure, not flagships. MyPlotter got its next version drafted on paper. Foreman got a one-line doc note, Havnetryk its nightly data export, and my ideas repo tracked all of it in eighty small entries.
Tonight: the trip site is built, verified locally, and waiting on me to push it live.