Disclaimer: this node is being coded with several beers inside me, and more going down.

When I were a lad, computer club meetings were almost always accompanied by substantial quantities of liquids. Some pretty sophisticated coding was done in these sessions. On the hardware side, two of my friends once came up with an overclocking mod for the TRS-80 model 1 when seriously liquidated. When they had sobered up, even with the working mod in front of them, they couldn't work out how they had done it. So I, for one, would hesitate before condemning alcohol as necessarily bad.

When programming for fun, I have no qualms about having a beer handy. I'm trying to relax, and a beer is part of that relaxation. Even when programming for work, I will often have a beer handy if I'm working at home (i.e. almost certainly in my own time). More than once, I have cursed a knotty problem, packed up for the night, gone home and suddenly spotted a simple, elegant solution after a few drinks. This is leading me to these conclusions: 1) Relaxation is important. 2) Complex solutions can be solved better by a relaxed mind. 3) Beer is part of my relaxation pattern.

Against this, though, I have to say that, for me, study is something that has to be done stone cold sober. It's also worth mentioning[1] that I have more than once been so engrossed in a problem that I have ended up with a nearly full can of flat, warm beer!

I also spend a lot of time under the influence of pseudoephedrine (an amphetamine banned by the IOC). It's an ingredient of my hay fever tablets, and certainly improves my coding. I defy anyone to work sensibly when sneezing every five seconds, and spending much of the remaining time trying to find a dry spot on a handkerchief.

Regards,

John Davies

[1] On the assumption that any of this node or thread is worth mentioning!


In reply to Re: coding under the influence by davies
in thread coding under the influence by leocharre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.