The plan was simple: one log for everything. The miles before sunrise and the code after standup — they were always the same discipline wearing different shoes.
Why a training log
Every serious block starts with a promise to write things down. Paces, sensations, what broke, what held. This is that, except some sessions are written in TypeScript.
Expect three kinds of entries here:
- Shakeouts — short notes: a race report, a bug that fought back, a tool worth keeping.
- Tempos — medium efforts: how the MCP servers are wired, what periodisation actually looks like in week 9.
- Long runs — the deep dives. Fueling strategy and system design get the same respect.
The stack under this page
const stack = {
frontend: "Next.js — hand-rolled CSS, no component library",
database: "Postgres on Neon",
auth: "one admin, one bcrypt hash, one signed cookie",
bill: 0, // and it stays that way
};See you at 05:00.