23 lines
870 B
Markdown
23 lines
870 B
Markdown
|
---
|
||
|
|
title: Frame Rate
|
||
|
|
date: 2026-07-27
|
||
|
|
layout: column.njk
|
||
|
|
tags: [column, computing]
|
||
|
|
permalink: /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?
|