Goals, with milestones under them
The thing most tools leave out. A goal is not a task; it is a heading that tasks and habits hang off.
I’m Gianfranco. I build the systems that delete my own busywork, and I write down the ones that work.
Goals in one place. Habits in another. Tasks in a third. A calendar that knows about none of it. Every Sunday you rebuild the same plan by hand, and by Wednesday it is already a lie.
Placeholder. Two or three sentences that make the reader wince in recognition — the specific, boring cost of the thing being wrong. Name the Sunday evening. Name the tab you keep open. This is the only beat where being uncomfortably specific is the whole job.
Small, finished tools that remove one specific kind of busywork. Not a platform, not a methodology — software that does the boring part and then gets out of the way.
The thing most tools leave out. A goal is not a task; it is a heading that tasks and habits hang off.
Three times per seven days, never 9am Tuesday. The scoring is ported from Loop Habit Tracker and matches its own published numbers.
The field set is what tasks.org and Vikunja independently converged on a decade apart, rather than what I guessed at.
RFC 5545, checked against the specification's own worked examples in local time — which is where every daylight-saving bug hides.
A promise a reader cannot picture succeeding is worth nothing to them. This is the beat that makes the previous one credible — what it has already done, how long it took, and what it cost.
Every one of these started as something I was avoiding. What I tried, what broke, and whether the fix survived contact with a real week.
Gianfranco OlofernesPlaceholder. One sentence that says what lands in the inbox and how often — the last promise, made where the reader can act on it, with the sun up behind it.