Hmm. Well I'm surprised to hear this actually. Figure I'll reply here. I work on a lot of open source projects and have done authorship analysis, and they do te

Hmm. Well I'm surprised to hear this actually. Figure I'll reply here. I work on a lot of open source projects and have done authorship analysis, and they do tend to follow a power distribution. The thing is, I'm one of those authors that loves to make a bunch of changes. Fix this, fix that. I'll throw up a commit before I'll send an email about it. I love fixing things. I consider myself a programmer through and through. When I entered management, I don't get that "fix" at work, so I might code 9hr on a Saturday building something fun. I've always viewed it as a good thing. An escape, a joy, cathartic, and pleasurable. Perhaps sometimes, it's gone too far. I left a birthday party last summer to go back and code. Though, you see, I'm also trying to build something, to do something. So to see the full blown addiction behavior. It's like looking over the edge of a cliff. I don't think I would go that far, but for me the most important takeaway from the article was this too can be an addiction.