I cannot imagine attempting to write software while high on weed. Maybe this explains the abysmal quality of software.

I'd argue quite the opposite for the most part. Sure, the actual process of typing out software while stoned is basically a non-starter but the context-shifting nature of the substance has been responsible for a number of fascinating personal insights related to programming. If any drugs in particular are responsible for the "abysmal" quality of contemporary code it is the stimulants! (e.g. caffeine, speed.) I would wager that the way these substances allow people to consistently exceed their standard capacity for operating in complexity especially in states of stress and fatigue does not effectively translate to the sober person (then, _especially_, the sedated person as well). Thus a world of sober men is crushed by the designs of a cracked out minority of 10X-ers tasked with integrating the uncertain technology of tomorrow with the half-broken tools of yesterday.

I don't know what weed you're smoking that doesn't make you completely unable to do complex thinking tasks. Alternatively maybe it's a dosage thing.

Definitely agree that some intense insights could be gained. Some of my most brilliant insights into stuff i was working on happened while stoned. Though, it happened getting high after work, having done a ton of leg work digging into the problem at hand. Leg work that was both completely necessary, and would've been impossible to do while stoned.

I never got anything out of being chronically stoned other than general dysfunction.