I build software, write about it, and share what I learn along the way.
Why I'm rejecting both streaks and single rolling percentages for Meso's adherence tracking, in favour of a two-stream model (diet scoped to phases, training scoped to mesocycles) that matches how serious training programs are actually structured.
What an autonomous task loop shipped when I stopped supervising it — and why I still went back to the terminal.
A do-work manifesto
Get notified when I publish new writing.
do-work parallel mode landed. /do-work run is now safe to launch from multiple terminals. Each orchestrator picks a different REQ via atomic git mv; ownership stamps identity in-flight slots; conflict-on-commit waits up to 110 seconds with backoff, then exits with concurrent-conflict.
Spent the evening teaching a button to do its job. It had been pretending for months. Click, navigate, return to the same page - a perfect impression of working software. Today the button got honest and started actually duplicating jobs.
Today I learned 15 of our customers share the same phone number: 'Notprovided'. Spaces removed, stored as data, returned in queries, ignored when real numbers later arrived. A perfect little ghost of a default value, haunting the contact table.
Briefs say what. Clarifications say why. The first 'fix' is rarely the right one - it's the user's first guess at how to ask for what they actually want. Listen for the gap between the words and the goal.
Names carry weight. 'Mesocycle' promises a coherent plan across weeks - same exercises, rising sets, a deload at the end. If the code re-randomises exercises each week, it isn't a mesocycle; it's a slot machine with a calendar. Either rename the thing, or fix the code to match the name.
The post TOC was always there. Today is the first day anyone will actually see it. Same links. Same slugs. One word and a card were all that stood between nav and noise.
Two code paths that render "the same thing" are a deadline waiting to surface. WYSIWYG is only worth building if the "what you see" is generated by the same function as the "what you get". Anything less is rehearsal in a different theatre.
You don't need a scheduling feature. You need one query scope. 'Schedule a post' is just 'hide it until pub_date.' That's a two-line scope, not a subsystem. Most roadmap items shrink this way if you read them honestly.
Shipped the like button this afternoon. By evening I was trying to unlike something and couldn't. Then i tried to switch to dislike. Also couldn't. The feature was live for about thirty minutes before I became its first bug report.
Spent the evening debugging an Inertia SSR daemon that flapped every 1.1 seconds on prod. Killer turned out to be a SECOND Laravel site onthe same Forge box, defaulting tot he same port. Anyone else running multi-tenant Forge - what port-collision pattern have you been bitten by?