Written with Capture
How I Started Writing Articles While Walking and Running
I speak while walking or running, Capture keeps the fragments, and Hermes helps me research and shape them. These are the finished pieces.
Each article opens as a read-only Capture Thread. Where I’ve shared them, the source moments sit beside the finished work.
Articles
Read-only threadTwo Months of Removing Friction From My Own Life
I record a lot of thoughts while walking. Product ideas, things I want to change, bits of an article that I would probably overthink if I sat down to write it.
What My Quietest Days in Capture Had in Common
I noticed something in the heatmap of my saved thoughts. On the days when I’m tired, sleeping badly, stressed, or carrying too much, I tend to record less.
What Should Happen After I Capture a Thought?
I was reading Michael Steinberger's The Philosopher in the Valley, a book about Alex Karp and Palantir, when I stopped at a passage about data.
My Agent Broke Capture. Its History Helped Us Get It Back.
I put a thought into Capture and got one giant Action back. It was supposed to be broken into smaller things I could actually do.
Being on the Move Made Me Better at Building Products
At the beginning of this year, I went for a 5K run. Nothing unusual on paper. But afterward, I had to recover for much longer than I expected.
Everything in This World Can and Will Be Made Better
I’ve listened to Jim Jannard’s interview on Factory Pirate Radio four or five times now.
I Keep Removing Friction. Then I Build It Back In.
I have a very interesting problem: I like to overbuild and perfect things. This usually happens right after I solve something.
I Only Check X for Messages Now. Everything Else Runs Itself.
Most days, the only thing I open X for is to read a message someone sent me. Everything before that already happened.
I Made It Easy to Catch My Ideas. Then I Had to Learn How to Publish Them.
Building Capture removed the friction from catching ideas, but it also made the remaining work of writing, publishing, and finding readers impossible to ignore.
I Built Capture to Catch Ideas. Then I Started Walking to Find Them.
How walking became part of my thinking process, why a heat map can help or distort it, and what must happen after a rough thought is saved.
The Software I Can Use While Running
What a 27-minute run taught me about voice capture, preserving raw thoughts, and turning selected friction into verified product work.
Three Weeks Ago, My App Did Not Exist. Now I Use It Every Day.
I built Capture three weeks ago. The reason I built it goes back much further, to roughly 400 notes divided between Google Keep and Apple Notes.
I Lost Thoughts Because My Notes App Made Me Choose.
The thoughts I lose are never the clean ones. They arrive as one sentence with two things jammed inside.
Shared threads
Shorter pieces published straight from Capture. Each one takes an idea from someone else’s work and applies it to building Capture.
What should all this information help you decide?
An idea from The Philosopher in the Valley, about Alex Karp and Palantir, applied to the things a person saves for themselves: collecting it is not the same as making sense of it.
Nice picture. What does the product do?
A lesson from Jack Butcher of Visualize Value on explaining a product: show the change between two situations, before the screen full of features.
One more fix. Then I’ll show someone.
An observation from Vadim Zeland’s Reality Transurfing, applied to making things: when does improving the work turn into putting off the moment someone sees it?
Does the product earn the story?
From Jim Jannard’s Origins of Oakley interview: before improving the pitch, find the part of the product that gives it something concrete to say.