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

Comment on

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

He must have been “Agile...”   ;-)

Oopsie, so it did leak gallons and gallons of boiler-water ... but he wrote the code the first time real fast, didn’t he?   (And the second time, and the third, and ...)

Every piece of code that you write is worth writing well, especially if it is to be anywhere close to a production system.   And there is no elitism about saying that.   (Personally, I do not like code that I thought had been finished years ago, coming back from the dead to bite me in the asterisk.   I resent and despise poorly-written stuff that fails at three o'clock in the morning.)   When you put in a plumbing fixture, you have one chance to make a permanent and lasting impression on the client ... and you will in fact do so, either way.   The client expectation is that the fixture is the right one, properly installed, and of course it never leaks.   My predecessor obviously did not know the basic plumbing rule that a galvanized fitting cannot be attached to a copper piping system because it will corrode; as it did, which is why it broke off in my hand.   A professional plumber has to get it right the first time, even though (s)he is merely dealing with a low-pressure water piping system ... not something as vastly complicated as computer software.


In reply to Re^5: Perl Elitist Code vs Functional Code by sundialsvc4
in thread Perl Elitist Code vs Functional Code by morissette

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 taking refuge in the Monastery: (5)
    As of 2018-06-25 00:52 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (126 votes). Check out past polls.