The general concept of getting some distance from the problem and then - after letting go - get back to it with a clear mind is a very good solution, but creating this distance by using alcohol bears the risk of addiction. It should not be the usual way you "solve" your problems. Instead you could try to literally run away from them by running some miles or cook a good meal or do kung fu or meditaion or read a book, etc...
Just be careful.
There's no way I could write code whilst pissed or wasted. Couldn't possibly concentrate.
However, when I was somewhat younger (sounds like a four yorkshire men moment) and a mainframe engineer I did rock up to work stoned a couple of times. Worst was after a Cure concert ('bout 1981 or '82). My mate's older cousin was the Cure's manager so we ended up smoking some big fat numbers backstage afterwards and then I had to stagger off and do the nightshift. FAAAAARRRK. Never again.
If your neighbours don't listen to The Ramones, turn it up real loud so they can.
“We didn't have a positive song until we wrote 'Now I Wanna Sniff Some Glue!'” ― Dee Dee Ramone
"The Democrats want my guns and the Republicans want my porno mags and I ain't giving up either" - Joey Ramone
Back in the old days, when the HP 9825 was still in production, the three drink lunch was fairly common in the defense industry. Not only was our nation's strategic defense infrastructure designed and built by the low bidders; they were drunk half the time, too!
I'd day it'd be just the same as coding when you're sick or tired - you'd find it hard to concentrate, so it'd take much longer to do it properly and probably result in code that you will re-write later when you are back to normal.
When placing a bottle of Jack (with the occasional nip from it) next to my keyboard and turning the music loud (heavy metal at best).
I become in a rather relaxed state so I can finaly think and fix problems where I don't have the time nor peace for at work (where everybody is constantly trying to annoy me with stupid questions).
I must confess that I do a lot of documenting in the source when in a tipsy state; you never know when it crashes and what your thoughts were at that moment
Note: I code best when I'm drunk (at least I think so!)
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
Almost all the code I wrote in last 6 years is under the influence of nicotine (I know that doesn't count).
Once, I was at a party and got drunk. Apparently at the same time some some genius released an awesome piece of code on the production server which was having a butterfly effect and some remote module was crashing. So when our trouble shooting team could not fix it they called me up(it was very late at night). And that was the only time I went to office drunk and still brag about it because I found the cause of the problem in that mode too.
Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore, Dream. Discover.
Last Visit: 31-Dec-99 19:00 Last Update: 3-Feb-23 22:58