Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I tend to agree with you on your subject title.. I find that lots of people that I know, with significant development experience, know or do less than I do in terms of sanity checks...and I'm nowhere near perfect to begin with...

Its too early in the day for a rant, at least where I live :o), but I'll say it anyway... there are too many people who never bother to dissect all the code that they write or use or actually try to understand the inner workings of their system... Many (*I shamefacedly admit I may belong to this category*) have fallen into the MFC ClassWizard trap, so to speak.. we trust that the code we write is never going to crash, or that it's going to run perfectly the first time...

Sometimes though, its because of a genuine lack of time.. I've had to make conscious decisions to sacrifice complete robustness and error checking for getting the job done fast.. its an awful excuse, I know, but in the world that I work in, no one really seems to care how well I write the code or about what exceptions I handle, so long as it seems to work... rightly or wrongly, fostering that sort of attitude is bound to make people less conscious of the stability of their code, so long as you can push it out the door fast, then nothing else matters....

I think also that what you speak of has its roots in your professionalism and approach to work... if you're writing something merely to do a job, then you take no pride in your work... and you try to do the minimum necessary....

In my mind, the ultimate test happens when you have to extend/maintain/debug someone elses code... if anyone has to do that often enough, then these steps become automatic.. and that is only going to make a better programmer out of you...once stuff like writing readable code and appropriate error checks becomes automatic, then you have more time for the really cool stuff :o)

In reply to Re: Are debugging skills atrophying? by tinman
in thread Are debugging skills atrophying? 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (4)
    As of 2018-01-21 22:58 GMT
    Find Nodes?
      Voting Booth?
      How did you see in the new year?

      Results (230 votes). Check out past polls.