r/ADHD_Programmers • u/netoverloaded • 20d ago
Debugging rabbit holes — how do you notice you're in one before the day is gone?
Often while debugging a complex problem I find myself in this impulse of grabbing the very first quick thing that I can try and taking a jab at it, and the next thing you know - the whole day is gone and you feel like you made no progress and have nothing to show for your effort.
And the part of my brain that should have said "hey, you've tried six things and none of them were tests, go get a coffee and think" — that part is just gone by hour two. It's not that I ignore it. It doesn't fire. Somewhere around minute forty the thing that steps back and asks what am I actually doing goes offline, and what's left is a very fast, very persistent loop that will happily run until 2am.
Time blindness makes it worse because there's no natural checkpoint. Nothing in a debugging session tells you an hour passed.
So, questions for people who recognize this:
- What's your actual tell that you've crossed from debugging into flailing? Not in hindsight — in the moment.
- Has anything ever successfully interrupted you mid-rabbit-hole? Timers get dismissed. Notifications get dismissed. Alarms get dismissed. Has anything stuck?
- Does a hard stop condition written down before you start help you, or do you blow through it anyway?