I stopped watching my AI think and ran two things at once
Have you ever felt time just leak away while you sit there watching your AI “think”? Nothing to do for those thirty seconds, so you open Instagram, scroll a few reels, and then look up to find the AI has been waiting on you for two minutes, needing you to hit enter for the hundredth time that day so it can go think some more. And now you feel worse, because you weren’t quick enough, and the whole thing crawls.
That was me for the last two weeks.
Honestly it didn’t feel like much of a problem at the time (thank you, algorithm, for the endless Haaland reels and FIFA clips). But now that it’s fixed, I’ve had to rethink how I spend my time. All those hours, gone, so one line of work could crawl along in order while I babysat it.
Then a thought hit me, and brace yourself for how groundbreaking it is. What if I opened two windows and worked on two things at once?
Revolutionary. I know.
While one session went off to think, I’d already be feeding the second. Two became three almost immediately, then several. I got a little hooked. Suddenly I had a handful of parallel workstreams going, hopping between terminals, always something to do, never staring at a spinner. They even shared the same project and interleaved their work without stepping on each other, which I’d expected to be a disaster and it wasn’t.
I’d flagged this exact thing a few nights earlier, while building a scorekeeper for my AI. I’d said the fix would be about how I work, not more code. This was it.
So, sorry Instagram. You were good to me these two weeks, but the AI turned out to be better company. My dead time is gone, and I didn’t upgrade a single tool to kill it. I just stopped waiting.
If you feel slow with these tools, watch yourself for an hour. I’d bet the bottleneck isn’t the model. It’s you, standing over the microwave.