
I keep losing 15 minutes to interruptions that only lasted 2 minutes
You know I've noticed this happening a lot when I'm working.
A Slack message, a quick meeting, someone asking me something the interruption itself isn't usually a big deal.
The annoying part is coming back.
I know what project I was working on, but sometimes I can't remember exactly where I was in the thought process.
Why was I trying this approach?
What had I already ruled out?
What was I about to test next?
Then I end up opening files, reading old notes, checking Git changes, and basically trying to reconstruct the last 15 minutes of my brain.
I've tried leaving TODOs and notes for myself. They help with remembering the task, but they don't always capture the reasoning behind it.
That's the problem I've been experimenting with.
I built a small Windows app called Anchor for myself. Before stepping away, I can leave a short checkpoint about what I was doing and where my thinking was. When I come back, I can read that checkpoint instead of starting the reconstruction from zero.
I'm still figuring out whether this is actually useful or just another thing to maintain.
If you've experienced this, I'm curious about the actual experience, not what tool you use:
When you come back to a task after an interruption, what is the thing you find yourself having to reconstruct?
If you'd like to actually try Anchor for a week and tell me where it breaks, here's the project:
https://github.com/Roshiyadesign/Anchor
It's a free Windows beta. I'm looking for people who will actually use it, not people who just want to tell me whether the idea sounds good.
If it doesn't help, that's useful too.