I wrote this from my phone, on a couch, half-listening to friends. By the end of the same night I'd also helped a friend stand up his own AI assistant. None of it felt like work. That gap — between "I have an idea" and "the thing now exists" — has quietly collapsed to almost nothing, and I don't think we've noticed what that does to us yet.
Between drinks, from my phone, I helped a friend stand up his own AI agent. We weren't at desks — we were out, the conversation lulling, my hands half-busy — and over the evening, in the gaps between everything else, his own agent came online. His, not a copy of mine, wired to the things he cares about. None of it felt like work. A thing that would once have been a "let's find a weekend for it" project just... happened, in the background of a normal social night.
There's a specific dead time I've been feeding to my phone for years. Waiting for coffee. The middle stretch of a night out when the conversation lulls. The twenty minutes in bed before sleep. Historically that time went one place: I'd open something, scroll, and hand my attention to a feed designed to keep it. I'd surface twenty minutes later having built nothing, learned nothing, felt slightly worse.
For the last few months that time goes somewhere else, and I want to describe the change honestly because I think it's bigger than it looks.
I have an always-on AI assistant (his name's Max — yes, 👽) — my own setup, running on my own box, that I talk to from my phone the way you'd text a very capable friend who never sleeps.
And what I've noticed is that the little gaps in my day tip a different way now. I was never much of a scroller to begin with — but whatever those minutes used to be, the ones that would have drifted to a feed, I now build in instead.
I call it micro-coding: shipping real things in small conversational bursts, from wherever I happen to be, in the cracks that used to belong to the feed. We've made our peace with micro-learning — knowledge in the gaps. Micro-coding is the same move, pointed at building instead of consuming.
🧩 What micro-coding actually is
It is not "vibe coding" and it is not sitting at a desk. The defining constraint is the situation: I'm not at a keyboard, I have maybe ten free minutes, and my hands are busy or my attention is split. The old version of me could not build anything under those conditions. Building required a laptop, a quiet room, a loaded-up mental context, an hour minimum. The activation energy was high enough that most ideas just... died in a note somewhere.
Micro-coding is what happens when that activation energy drops to the cost of a voice note. I describe what I want out loud. The assistant does the part that used to require the desk — reads the code, makes the change, runs it, tells me what broke. I course-correct in a sentence. The loop that used to take an evening now fits in the time it takes to wait for a drink.
The unlock isn't that AI writes code. That's old news. The unlock is that the friction around starting has gone to zero, and friction was the whole reason ideas didn't become things.
🌙 One night, as proof
I'm not theorizing. Here's what one ordinary night actually contained, all of it from my phone, most of it while I was physically hanging out with people. The friend's agent up top was one half of it. Here's the other.
I pushed a real project forward without opening a laptop. Same night, same phone, I dropped a task into Talos — the autonomous builder I keep running for each of my active projects. Two sentences describing the change I wanted, and it took over: pulled the project's context, planned the approach, wrote the code, ran a self-review, and handed back a structured completion report while I stayed at the table. All I did was say what I wanted and judge whether what came back was good enough. That's the version of micro-coding that actually scales — not me narrating code into existence, but me spending short bursts of judgment from a phone while the building happens elsewhere.
Neither of those required a desk or an uninterrupted hour. Both were micro-coded — narrated in fragments across a normal social night, the way you'd text a friend a half-formed thought, except these friends can actually build.
⚡ The mechanism: idle attention becomes raw material
Here's the reframe that matters to me.
For a decade, my idle attention was somebody else's product. The feed's entire business was to convert those dead minutes into engagement. What micro-coding does is reclaim the same minutes as build time — turn the exact attention that used to be extracted from me into the raw material for making things.
That's not a productivity hack. It's a change in what idle time is for. The scroll gives you the feeling of activity and leaves nothing behind. A micro-coded burst gives you the same low-effort, dopamine-adjacent hit of starting something — except at the end of the week there's a thing that exists. Same posture, same fragments of attention, opposite output.
And it compounds in a way scrolling never does. Every burst leaves an artifact. The feed leaves a history you're vaguely ashamed of.
And those artifacts add up faster than the size of each burst would suggest. A few of the things I've stitched together this way, entirely in the cracks of ordinary days, have quietly turned into something I'm genuinely proud of — more on that, perhaps, in a later post.
🎯 The catch: the bottleneck is now taste, not tooling
I want to be honest about the ceiling. When building gets this cheap, building stops being the hard part — anyone can generate ten apps, a hundred landing pages, before lunch, and most of it will be slop. So the scarce thing is no longer the ability to make; it's the judgment of what's worth making, and whether what came out is any good. The bottleneck moved from your hands to your taste — and taste doesn't come from a voice note.
💭 Where I've landed
I'm not going to pretend this is all upside. Reclaiming idle attention from the feed is a real win. But it hands you a new responsibility that's harder than the old one: now that you can build anything in the cracks of your day, you have to decide what actually deserves to exist.
That's the trade I'll take. I'd rather spend my dead minutes making things I have to stand behind than scrolling things I'll forget by morning. The feed wanted my attention. I'd rather it built something.
The tidy proof of all of this is the thing you're reading. I didn't sit down to write it. I dictated it into my phone, in fragments, on the same couch, between the same conversations — an idea, a correction, a "no, say it like this," a "make the tone drier." It was micro-coded like everything else that night, built back and forth with my agent. If it reads like something a person sat and wrote alone, that's worth being honest about: it wasn't. The gap between an idle thought and a finished artifact is now one honest voice note wide.
Now, back to my friends. This one's shipped.