Maybe here's the anatomy of the addictive aspect Let's say you have a web idea, its so "simple". So you code it and do a "proof of concept". Then you start c

Maybe here's the anatomy of the addictive aspect Let's say you have a web idea, its so "simple". So you code it and do a "proof of concept". Then you start coding, you think you have it nailed, you predict you can do this thing in a few thousand lines of code using bla bla framework. So you write those few thousand lines of code. Its done. It works. Except, it doesn't scale, it has no security, you have no hosting, load balancing, failover, replication, user authentication, marketing, no decent website, no android or iOS presence, no enterprise customers, it looks like crap, you have no graphic artists, you have no CSS experts, you do OK on those but its not professional. And then the features: the "real" product you wish you were building is beyond your means. Sure you can try to patch it together, but your "few thousand" lines of code delusion is just that. That's a sure sign of code addiction. And Ive been there myself. Its not that you CANT do all of those things. Its that you spent your time ignoring all of those things to justify coding. And when you hit that wall, you will most likely stop in your tracks and ditch your idea and the work you put into it, to focus on your next "thing".