Stephen Donahue
c6d7c8c211
Some checks failed
Deploy to S3 / deploy (push) Failing after 1m24s
Retract the seven published columns into drafts/ and promote the 24 per-date entries split out of Notes/random.md. Bodies are verbatim; titles, subjects and slugs are new. Make publication a matter of location. Notes/Notes.11tydata.js gives anything under Notes/ permalink: false unless tagged `column`; drafts/drafts.11tydata.js renders drafts at their real permalink under `yarn dev` and excludes them from collections entirely in a build, so no template can surface one. Publishing is now `git mv drafts/<file> columns/`, and moving it back retracts it. Untagged notes were previously rendered into _site/ and deployed — including Notes/random.md, which was live at /Notes/random/.
870 B
870 B
title, date, layout, tags, permalink
| title | date | layout | tags | permalink | ||
|---|---|---|---|---|---|---|
| Frame Rate | 2026-07-27 | column.njk |
|
/columns/2026/frame-rate/ |
We think in Fragments
We're back at mainframes and teletypes. An enormous offsite compute resource. You dial in with your client.
The same practice - get your batch jobs ready to run overnight, over the weekend. Spend the daylight hours collaboratively tuning, refining, testing.
The prep for the night to come, and for the day after, the next repeating link.
And mistakes were expensive. Something faulted, the job failed overnight. You spend the next day(s) troubleshooting.
Did it feel expensive back then? Or has the frame rate of our lives gotten so high that a span of days feels closer to eternity?
every session branching through alternate realities - do you know when you're on the 'good timeline?' Do you know when you're not?