Interesting point of view, especially the 'psychological' aspect ('fever' excuse).

And even If I'm sure it works, for my part I rather use a methodical approach :

1) Don't assume everything even OBVIOUS things
2) Find where the code begin to diverge from what is expected.
(I use a kind of dichotomic process with print to ensure that the values produced are those expected until I find the point where it begins to mess)
3) print is the coder's friend.
print everything possible during each step around the spot where you think the problem is...

But as I've discovered that the psychological aspect is VERY important.
I try to handle it like a challenge (finding bugs IS A GOAL); I've decided that coding with bug is normal(ie: I'm normal ;-) and that finding bug quickly is a skill...
This used with my formal method helps me to debug my code with pleasure (I'm improving my skills) and without a 'ego lock'...

As you see even if our excuse (for not being 'guilty' of finding a bug) is different the point is that we only have to manage to believe it, to prevent 'ego lock'...

Sorry but my poor english doesn't allow me to translate 'ego lock' efficiently, anyone got an idea?

In reply to Re: Tricking Our Egos by arhuman
in thread Tricking Our Egos by dws

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, 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, 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.