[sophacles]

I program high often. It's resulted in good code and bad code at proportions roughly equal to sober programming. The difference is generally in which code is good in each case.

Tricky memory stuff, trying to deal with complex order of operations (threads, race conditions, etc) tends to go way better sober.

House keeping like light refactors (im in rust these days so stuff like: oh that should be a result not an option, or using matches instead of ifs, genericize this struct), boiler plate stuff and cleaning up logs/error handling tends to go better when I'm high.

But there are exceptions to both trends and I've done good deep work high and done plenty of good housekeeping sober. And of course since it's coding, i've (re)done plenty of bad work in both states too.

Sad to know my experience is just nonsense. I guess I need to get in touch with the CFO and let him know the profit from the product I wrote is just a pipe dream.