On the quiet after the Process,
and the argument for slower software.

For two years I have kept a plain text file called morning.txt. It contains the day's decisions, none of them synced. What that discipline has cost me — and what it has quietly returned.

The last time I opened the Process — our team's real-time board, seven columns wide, sixty-three lanes deep — it was a Tuesday in February and I stood at the kitchen counter with a cooling cup of tea, watching a colleague in Lisbon rewrite the title of a task I had written the night before. It was a small edit, the kind that means nothing. I closed the laptop and did not open it again for eleven days.

What I noticed first, unromantically, was that I slept better. What I noticed second was that the work — the actual argumentative shape of the essay I owed the desk — kept moving forward in a way it had not moved for months. I began keeping the file I mentioned in the dek. Every morning I wrote three lines in it. Every evening I crossed one out. No one was notified.

A quiet argument for tools that do not watch you back

There is a species of software — Cloudbank readers will know its shape — that treats attention as a substrate to be strip-mined. It pings, it batches, it renders your absence as a colored dot. My proposal is smaller than a manifesto. It is only this: keep one instrument on your desk that has no telemetry, no cursor beside your name, no small green light announcing you are here. Let it be plain. Let it be slow. Let it belong to you alone.

"The room stayed the same. What changed was that no one else was in it, watching me arrange the furniture."