[PopeOfNope]

I wouldn't qualify this as an addiction either[0], but it's still good to know what motivates programmer behavior and the dopamine cycle is definitely a factor. The real question is how do we use this information in a productive way (better code quality) rather than a destructive way (needless code complexity).

[0]: My personal definition of addiction is, if you were to stop doing X activity for a week cold turkey, would you experience withdrawal symptoms?

[outofcuriosity]

People barred from flow often experience intense anxiety; I'd imagine that the "addicted" programmer not experiencing code flow would just replace that need with something like a high-complexity videogame.

The author's scope is maybe too narrow by focusing only on programmers. Perhaps this problem can be generalized to a type of individual that requires the flow state to the extent that their other behavior is perturbed or dysfunctional. Compare Richard Feynman's explosive rage when distracted from calculus or drums...

[goldfeld]

Yeah, when I had to stop dancing--an activity that gives me a flow experience every day--for weeks because of a twisted foot tendon, I became a mess of anxiety, and even resorting to singing sessions wouldn't quite give me my "fix", or fix me so to speak. Likewise, it's not about having to stop programming, it's about, for example, having to stop working on a project in which you have lots of daily momentum and flow. I think it's a proper addiction. Now if it's just half-hearted programming, nobody misses it much.