This article isn&#x27;t really about the &quot;<i>effects of programming on the brain.</i>&quot;<p>Instead, the author has a pre-determined value judgement of what is a &quot;good&quot; or &quot;bad&quot; allocation of priorities.  From that premise, he works backwards to a observation that coding can be addictive.  This addictiveness is then judged as &quot;bad&quot;:<p><i>&gt;someone who may be suffering from what I can only really describe as coding addiction, the solution may be to find healthier rewards.</i><p>For some people, the healthiest reward <i>is the coding</i>.  For others, it&#x27;s working on solving a 300-year old math problem, or struggling for hours and days to find the perfect word for a line in a poem, or a sentence in a novel.  There are no &quot;healthier&quot; rewards than those intellectual gymnastics.<p>Sometimes it&#x27;s true that these &quot;addictions&quot; don&#x27;t perfectly align with business priorities and client demands.  Saying that the addiction is &quot;unhealthy&quot; is favoring the perspective of the business.  The other perspective is that the individual is in the &quot;wrong&quot; day job.