should I get drunk then code, or should I code then get drunk?

will the results be any different whichever I choose?

drunken coding is fun in any case

Depends, if you know what you want to code, code then get drunk. If you don't know what you want to code, try it the other way round!

CWI can be dangerous. I advocate coding while sober, then drinking. Debugging drunken code can be very laborious.

i wholeheartedly agree.

which is why I am now here several hours later stone cold sober but feeling quite chirpy about the evenings progressions

last time i had a tipple i spent the entire next day with a wtf look on my face.

At least if you use a version control system you can easily go back to yesterday's version, then work forward again cherry-picking the best bits of your drunken coding.

one big computer and intoxicant nono is the setting off passwords...

tso, that sounds like the voice of experience

not really, but given the number sillies i have done while drunk, i worry what kind of insane password i may end up with...

Yes, but curiously the rather odd structure I use in my drunken code always seems to work, despite my needing a day or so of sober debugging to check that it does what I wanted (obviously if I got drunk again I'd probably immediately understand what the code was doing)