ADHD and Software Engineering: A Task System That Survives Context-Switching
The job rewards long, unbroken focus. Your day is built out of interruptions. That gap is exactly where the ADHD brain gets stuck — and where a short daily reset does the most work.
Software engineering can feel like it was designed both for and against the ADHD brain. The deep, absorbing problem-solving is the part many ADHD developers love — the hours vanish, the code flows, and hyperfocus becomes a genuine superpower. But the rest of the job — the ticket queue, the context-switches, the standups, the "quick" Slack question that derails an afternoon — is where the same brain gets quietly wrecked. If your commits are excellent but your task list is chaos, this is for you.
Why coding with ADHD is uniquely hard
To write non-trivial code, you have to load a mental model into your head: the data flow, the edge cases, the three files you're holding in tension. That model is expensive to build and fragile to hold. Every interruption — a mention, a PR review request, a "got a sec?" — dumps it. Neurotypical brains rebuild the model with some friction; ADHD working memory often has to start almost from scratch. The industry has a number for the reload cost, and for an ADHD developer it runs higher and hurts more.
Then there's the queue. Jira, Linear, GitHub issues, review comments, that flaky test you keep meaning to fix — the backlog grows faster than any sprint burns it down. When every open ticket sits in view at the same volume, your brain scans the whole wall every time it tries to pick what's next, and on a limited working-memory budget that scan is exhausting.
Your issue tracker is a library where every book has been pulled off the shelf and stacked on one table. Nothing is lost — but you can't find the one thing that matters right now, because there's no structure telling you where to look.
Hyperfocus and time-blindness — the double edge
Two ADHD traits shape a developer's day more than any tool does. Hyperfocus lets you disappear into a hard problem for hours — brilliant for shipping, dangerous when it's spent gold-plating a refactor nobody asked for while the release-blocking bug waits. Time-blindness — Russell Barkley's term for the ADHD brain not naturally feeling the passage of time — is why your estimates drift, why "this'll take twenty minutes" eats the morning, and why a ticket due today and one due next month can feel equally urgent.
Put together, they explain the classic ADHD-engineer day: you go deep on the wrong thing, look up at 4pm, and realise the two tasks that actually mattered never got touched. The problem was never focus. It was aim.
It is not a discipline problem
This is worth saying plainly, because the shame does real damage in a field that prizes output. No engineer clears every ticket assigned to them. The backlog is supposed to exceed throughput — that's what a backlog is. Neurotypical brains are slightly better at unconsciously letting low-priority tasks fade; ADHD brains tend to capture every ticket, idea, and "I should really…" with equal intensity, so the list grows and starts to feel like evidence of failure instead of a normal engineering queue. It isn't. The math doesn't close for anyone.
The reset, applied to your workflow
The fix isn't a new app — you already have five. It's a smaller thing to look at. You break the freeze by shrinking the decision until your brain can make it, and you make it survive interruptions by writing down where you were.
1. Let the tracker be your Inventory. Your whole backlog — Jira, Linear, issues, that mental list of tech debt — is the Inventory. Its only job is to hold work safely so your brain can stop guarding it. You do not act from the Inventory. You do not even look at all of it.
2. Pull three tasks into Today. Not the sprint. Not ten tickets. Three (four if you're pushing it) — the ones that actually move the release, the revenue, or the blocker. Everything else is invisible until you choose it tomorrow.
3. Write the next physical action as a command. Not "fix the refund bug" — instead, "open payment_service.py, write a failing test for the double-refund path." Engineers are already good at this; it's just the first line of a plan. The concrete next action is also your re-entry point: when an interruption dumps your mental model, that line is the breadcrumb back in.
Three tasks is not arbitrary. ADHD working memory reliably holds only a few items; three is a count you can carry through a day of standups and Slack without re-reading a board every twenty minutes. Seven is a fantasy — you'll reload the whole list each time and pay the switching cost twice.
Why this works — the science
In the 1920s, Bluma Zeigarnik found that unfinished tasks occupy more mental space than finished ones — every open loop keeps running in the background, draining memory and attention. For a developer that's every un-triaged ticket humming at once. Decades later, Masicampo and Baumeister (2011) found the hopeful part: you don't have to finish a task to quiet the intrusive thoughts about it. Simply making a specific plan for when and how you'd handle it was enough for the brain to let go.
That's exactly what the reset does. Moving a ticket to the Inventory tells your brain "this is tracked and safe — stop holding it." The three-item Today list tells it "these matter; everything else is handled." And the written next action means each interruption costs you a glance, not a full rebuild. The wall becomes a short, executable list.
This is the core of a short, ADHD-friendly system — tool-agnostic, so it runs on top of whatever tracker your team already uses.
Get The ADHD Task ResetCommon questions
Why is software engineering so hard with ADHD?
Coding demands long, unbroken concentration to hold a mental model in your head, but a developer's day is built out of interruptions — Slack, standups, code review, incidents, context-switches between tickets. Every interruption dumps the model you were holding, and ADHD working memory struggles to rebuild it. Hyperfocus helps you go deep but makes it hard to stop, so time-blindness turns a two-hour task into a five-hour one. It's a mismatch between how the work is structured and how the ADHD brain manages attention and time — not a skill problem.
How do I stop context-switching from destroying my day?
You can't remove every interruption, but you can stop them from erasing your plan. Keep your whole ticket backlog in one Inventory you don't have to look at, pull only three tasks into Today, and for each write the exact next code action — "open payment_service.py, write a failing test for the refund path." When an interruption hits, that written next action is the breadcrumb that lets you re-enter the task without rebuilding the whole mental model from scratch.
Why are my time estimates always wrong with ADHD?
ADHD comes with time-blindness — the brain doesn't naturally feel the difference between a task that takes one hour and one that takes five. That's why sprint estimates drift and "quick fixes" swallow an afternoon. The fix isn't to estimate harder; it's to shrink the unit you commit to. A short daily list of three concrete next actions is something you can actually deliver, which makes your day predictable even when your estimates aren't.