random interruptions aren't the problem, it's having to drop de-coupling work in a RTOS that I'm 3 days into when I get a support request that requires me to do the same in a second codebase, and then a phone call about a project I just deployed.
I thought I was just an idiot, now I realize I was at a bad company; but [my inspiration is gone] it's too late for that now
Maybe it's because I don't tend to work with really bad codebases that force me to keep huge mental models in my head while I'm making changes. Or perhaps I'm fast at getting ideas onto paper so that the stuff I need to keep in memory remains small. Either way, the dynamic the article describes is not an absolute, universal thing. There are environmental / behavioral factors at work besides "Developer, Interrupted."