I don't think I've ever had a bad drunk coding experience. Most of my nightmares involve being sober and doing this thing called "my job", which just seems like a terrible idea before I've even begun.

i tried it once, gave up after half a line of code

Our director bought us beer to bribe us into 45 to 60 hour work weeks instead of whiskey.

I can barely code properly while sober. Why would I introduce drunkenness into that equation? If drinking impairs driving heavy machinery, by what logic would it do anything to improve writing code?

All drunk coding experiences are the worst

I have a few colleagues who code best when slightly drunk. So I gave it a try a couple of times. That didn't work - I immediately felt drowsy and sleepy.

In general, I don't drink. I like it when my mind is razor-sharp and works better than a swiss watch, and even tiny amounts of alcohol spoil that clockwork for me. So drunk coding is not for me.

is "drunk coding" really a thing? i can't imagine how.

i prefer working code, so when i'm writing code, i need my brain to be working. the "benefits" of alcohol, like reducing social inhibitions, don't benefit source code.

Can't remember

Not me the multimedia dev intern helping the IT guy how to use excel

usually the worst drunk coding problem i have is leaving nasty comments in the code about the previous maintainers. Or ranting more vehemently on here than is really warranted... ;)

In other words it doesnt affect my coding, it just affects my social skills.... lol...

I only have good ones; my rule is never ever to publish anything while drunk so it's either a breakthrough or in the worst case a fun evening (at least compared to the alternative of sober coding)

Never had a really bad experience. Was just too tired to continue some times after getting tipsy. But I'm always faster.

"Worst drunk coding experience?"

My alcohol tolerance is very low. So, every stupid attempt of my coding in such a state is the worst experience.
There's this pulsing feeling in my skull every 10 seconds blocking my attention.
And there's an increased chance of mistyping commands.
One time, for some reason, I kept "pulling" the git commits when I actually wanted to "push" them. I spent a lot of time finding out why the f*<k GitLab is not showing my new commits in my PR before realizing my sheer stupidity.
And it takes me only one 3.5dl can of low alcohol content (like 3% abv) drink to relive these experiences. WTF.

“Sticks and stones will break bones, but the gat will kill you quicker, especially when I’m drunk off that liquor”
- Biggie smalls