You finally had it. The whole problem was loaded into your head — the data flow, the three functions involved, the half-formed fix. Then a teammate dropped by with a "quick question," it took ninety seconds, and when you turned back to the screen the entire mental model was gone. Now you're staring at code you wrote twenty minutes ago like a stranger left it there.
Every engineer pays this cost. For ADHD engineers, the bill is brutal. This article is specifically about that — context-switching, fragmented attention, and how to defend the deep, continuous focus that technical work depends on.
Why interruptions cost an ADHD brain more
When you're deep in a complex problem, you're holding a fragile structure in working memory — relationships, assumptions, the thing you were about to try. Rebuilding that structure after a break is context reconstruction, and it's effortful for anyone. For ADHD brains, two things make it far worse.
First, working memory is leakier, so the structure collapses faster and more completely when something knocks it loose. Second, the return is hard. Re-entering an unfinished, un-fun task is exactly the kind of task-initiation problem ADHD makes painful — so after the interruption, you don't just have to rebuild the model, you have to drag yourself back to a thing that's no longer interesting.
The interruption itself is cheap. The expensive part is the climb back into the headspace you fell out of — and ADHD makes that climb steeper.
That's why a day full of "small" interruptions can leave you exhausted with nothing shipped. You spent your fuel re-entering, not engineering.
Make the interruptions visible to others
A lot of interruption damage comes from teammates who genuinely don't know they're doing it. To them, a quick ping is free. They can't see the structure they just knocked over. So make it visible — kindly and concretely.
- Set a status that means something. A "heads-down until 11, back after" message trains people to batch their asks instead of firing them in real time.
- Name your focus blocks out loud. Tell your team you do deep work in the mornings and are reachable in the afternoons. Most people will respect a stated pattern far more than a vague hope.
- Offer an alternative, not a wall. "Can you drop that in the channel and I'll get to it at noon?" gives the person a path without requiring you to context-switch on their schedule.
You're not being difficult. You're explaining that your attention has a setup cost, and asking people to help you not pay it forty times a day.
Defend the calendar before the day defends itself
If you don't block time for deep work, the day will fill with everything else, and you'll do the hard thinking in the cracks — which is exactly where ADHD focus performs worst.
Put the deep work on the calendar as real, defended blocks, ideally aligned with when your brain is sharpest. Batch your meetings into clusters so you're left with genuine uninterrupted stretches rather than a Swiss cheese of thirty-minute gaps that are too short to enter flow but too frequent to ignore. And protect at least one block where notifications are fully off — not snoozed, off — so a single ping can't dissolve an hour of assembled context.
Survive the interruptions you can't prevent
Some interruptions are non-negotiable. Production is on fire; the standup is the standup. The goal there isn't to block them — it's to make re-entry cheap, so the climb back costs you minutes instead of the afternoon.
The trick is to leave yourself a breadcrumb before you switch away. When you have to stop mid-problem, take ten seconds to type a note to future-you: what you were doing, what you'd just figured out, the exact next thing you were about to try. A half-finished comment in the code, a line in a scratch file — anything. ADHD working memory won't hold the thread across the interruption, so write the thread down and let the note hold it for you.
The same goes for code review, another notorious context-switcher. Reviewing someone's PR yanks you out of your own mental model into theirs. Batch reviews into a dedicated window rather than answering each one the second it lands, and breadcrumb your own work before you switch over.
When fragmentation becomes a real problem
A caveat worth saying plainly: if interruptions and switching are leaving you constantly behind, burned out, or dreading work, that's worth raising — with your manager about your environment, and with a doctor, therapist, or ADHD coach about the underlying load. This isn't medical advice. It's a reminder that "I just need more discipline" is often the wrong diagnosis when the real issue is a work setup that fights your brain.
Most of the fix, though, is structural and within reach: name your focus needs, defend your calendar, and leave breadcrumbs so re-entry stops costing the earth. You're not bad at focusing. You're paying an interruption tax nobody told you about — and you can lower the rate.
When you need somewhere to drop that breadcrumb fast — the half-formed fix, the "I was right here" note, the thread you'd otherwise lose to a single ping — that's exactly what NoPlex is for: catching the context before it evaporates, so getting back in doesn't cost you the whole afternoon.