Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
I really like your idea and will certainly try it! If I can still fool myself by setting my watch fast then your trick is sure to work on me.

One thing that I learned long ago from a venerable old C hacker I worked for was the simple yet for me effective admonition that goes something like: "never stop at one bug" - I can still hear this in my head when I'm debugging (and no, the meds haven't helped ;-)! I have evolved two ideas from this:

  • if you're reading code and see something wrong (or you think is wrong), don't just "fix" it (possibly breaking it or something else more in the process) but keep reading until you fully understand what is going on.
  • even if you do fully understand a bug and fix it, keep looking as there could be more than one (well not in my code but there are people... ;-)
This was great advice back when compiling almost anything was at least a "get a coffee" event, if not a "come back after lunch" event, but I think this approach still saves me time even today when most of my stuff compiles in seconds. I often see people find a bug/error, edit the code to fix that one thing, then re-compile/run to get the next bug/error... that gets me cranky!

--
I'd like to be able to assign to an luser


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

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!
  • 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
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others cooling their heels in the Monastery: (11)
    As of 2014-08-29 22:29 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      The best computer themed movie is:











      Results (289 votes), past polls