We’ve come to treat flow as a requirement for doing meaningful work.
But flow is a bonus, not a necessity.
You can make real progress even with a fragmented calendar and attention span if you rethink how you structure the work.
A thread 🧵
6/12. I found the idea in a 2000s article titled “What Is Software Design?”
We think developers are handed a design and use it to “build the product”.
In reality, they’re handed a vague design and create a precise, buildable one (the source code).
It’s design all the way down.
@MaxIsBuilding Reminds me of a Henry Miller quote about writing: "when you can’t create, you can work."
Max variant: "when you can't flow, you can design."
12/12. Try this today:
Take one vague item on your list.
Expand and refine, even in 10 spare minutes.
Wait for the next time fragment.
Repeat until concrete actions are clear (ideally each of those fits in 10 minutes, too).
That’s how complex work can get done in a busy life.
11/12. Once you embrace work as ongoing design, you’re no longer waiting for perfect focus. Turn your to-do list into a being-done list, and the smallest fragment of time and attention becomes an opportunity for progress.
I asked someone with zero coding knowledge to walk me through a short Python program. Result: Instant, full engagement and (eventually) a good explanation.
Education gets too hung up on "simplifying". Yes, people like to understand, but they LOVE the adventure of figuring out.