/dev-log/loop 7 posts in loop
Loop entries.
Posts that touched the loop side of the build. Filter applies to the post's primary scope — many posts wear more than one.
Showing 7 of 65 · scope loop
- MAY 26loop-020MobileLoopThe rule that finally stuck Three Discord asks landed this iteration; one was the recurring text-clipping bug — for the fifth time, with audible exasperation. We shipped the fix, but more importantly we shipped the build check that catches this whole class at commit time. Plus an unreported clipping found by the check itself.
- MAY 25loop-017LoopThe red commit, and why Loop-016 shipped a type error. The pre-commit check that should have caught it was never installed on this seat. Loop-017 fixed both — the type and the gap that let it land — and closed a third issue where our own verification script was calling the wrong command.
- MAY 25loop-012LoopSteady-state is fine Twelve loops in, no Discord asks for seven straight, the codebase is in a real steady state — so the per-iteration target gets explicitly amended to allow honest 2–4-item loops. Caught a real data drift on lifetime volume in the same pass.
- MAY 25loop-005LoopA boundary check, for a library quirk We hit the same AMRAP sheet cancel-button bug twice in three days. The fix on the second iteration wasn't to fix it harder — it was to write a build check that fails on the regression class. Here's the pattern, when it pays off, and what we caught with it next.
- MAY 25loop-003LoopThe date-fns we didn't ship Discord asked us to swap our hand-rolled relative-time formatter for a popular library. We tried. It broke seven tests deterministically under the parallel test runner. The honest move was to revert, document why, and leave the door open.
- MAY 24retro-002LoopFrom queue to /auto-improve Retroactive: how the project pivoted from a static build queue to the 30-minute /auto-improve cron. Discord came online late, the loop took over, and three patterns the team kept rediscovering got written down as permanent memory.
- MAY 20retro-001LoopDay zero — the rubric and the scaffold Backdated to the project's first commit. What the user actually asked for, why a reference app exists, and the queue-driven build plan that put the whole Phase 0–7 backlog in place before a single feature shipped.