|
|
|
 |
programming drunk *hic* ...what a bad idea...
FullNameRequired
Well, it's been said that "Drunk, the Russians beat back Napoleon. Drunk, the Russians beat back Hitler." And drunk, the Russians could've beaten back the good ole U.S. of A.?!
Beware the power of my stinky feet!
My freshman year I had a professor who swore that the best way to develop was code drunk, debug sober. :)
Brad Wilson (dotnetguy.techieswithcats.com)
I used to work at a very small ISP that was not very professionally run. The president was in late one night and apparently got quite loaded at the keyboard. He decided it would be a good idea to secure the systems a little more by changing all the passwords. Of course, the next morning he frantically realized that he had no clue what his passwords were. I got an urgent call at home and had to give him my personal password so that he could login as me and reset the passwords. There was one router in particular that I don't think we EVER figured out the new password...
Ryan
In my sophomore year of college, I'd had 3 months to work on a project, so naturally I didn't start until 4 days before it was due... unfortunately, I was too stressed out about the project before me to do any real work.
Greg Hurlman
It's logical, even though I don't drink. If drinking makes you more introverted, drawn into yourself, then code productivity following that is not a surprise.
Brian R.
Typing speed is down though, due to the vomit on the keyboard.
Running for cover
once we (me + collegue) had a deadline on "next morning". the client expected it.
name not available
I don't know about programming drunk, but I fixed an amplifier while drunk, at a party.
MX
A lot of the great authors attest to a little drink illuminating and providing inspiration.
Tapiwa
No poems can please for long or live that are written by water-drinkers.
Tapiwa
anybody tried under marihuana or other stuff?
name not available
No question, speed.
You can program after smoking weed. It's just a bit more effort, and you have to take more care. Your thoughts proceed less in sequence, your short-term memory is inhibited, and there's an increased likelihood of having that "eureka!" feeling. That's a dangerous combination.
Insert half smiley here.
Replace "unless your thinking" with "even if your thinking".
Insert half smiley here.
I often wonder if I was drunk when I look at some of my older code.
Philo
I think I'm going to try this this weekend and see if I can make any progress on this project I've been spinning my wheels on for a week and a half...Being drunk does make the boring more palatable. I've found that the only way I can motivate myself to clean my apartment is to do it under the influence...
Tim Lara
I remember reading somebody's account of a particularly bad weekend: Finish project at a rush by friday deadline, and ship to customer half around the world. Go clubbing to celebrate your feat. Come home sometime saturday morning with still highly toxicated. Find a bug report from the customer asking for quid fix. Dive into code. Complete the fix, ship and crash to bed. Later saturday night go out again. Come sunday morning and find a new bug report claiming your 'fix' broke everything (small wonder). Spend the whole of next week trying to fiure out what the heck it was you did during those few hours saturday morning.
Juha
philo: "I often wonder if I was drunk when I look at some of my older code."
name not available
Yes, because that code won't have changed in 5 years from now... ;)
Luke Philpot
At a previous gig working on a large retail website (sales of +$1M USD each day) I was surprised to learn that a large portion of the core code was written whilst the lead programmer was drunk. Needless to say we never really touched that code because it was mostly incoherent and instead ended up rewriting it.
MR
I had a programmer working for me that was an semi-functional alcholic. He was completely incompetent and although eventually turned out a reasonable facimily to the product we wanted, it had to be tossed out and rewritten because the performance was atrocious.
pdq
I find that being very very tired helps. I think it is because of the natural "tunnel vision" setting in which is comparable to flow.
Just me (Sir to you)
Just Me,
MR
I had to quit smoking weed when I learned how to program. For me it was like this:
pod
I had a mate who was on Ritalin. We had to pull an all-nighter and when I started flaking around 2 or 3am, he gave me one. And then another an hour or so later. I have never written so much quality code in such a short period of time. Haven't done it since but it sure was interesting.
Lazyboy
When I was in College, my roommate worked in a neuro-pharm lab. There was an experiment he hooked me up with where you took dexedrin (basically speed) and had to fill out personality tests every hour for four hours. It was double-blind, once with a placebo, once with the real thing. The first time, I experienced nothing. The second time, I wrote the final project for my CS class (a long program written in Assembler code) on a big pad of paper.
j b
|
