Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Comment on

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

I wrote a CGI application that was to be incredibly simple, just a portal for user-defined links. This program, while being written, experienced many design/function changes from above. I had to patch code together to get it done quickly (the client didn't know that changes = time); in the end, it's become an ungodly mess. It usually takes me five minutes to find a problem, and 30 seconds to fix it. I dread doing an update for my code has become "write-only."

I'm writing some new code in my leisure time. I could have written without and source formatting or comments, but I know from my previous experience that updating badly formed code takes all the fun out of programming. I've had many side projects die because in my hasty attempt to complete my idea before it left the station without me aboard, I left no clues for me to pick up where I had left off. This recent "fun" project is taking longer than expected, but it's worth it.

I think that given certain outside variables (your %ENV :), one should choose between the quick-and-dirty or the refined, elegant method. Both have some advantages and disadvantages (namely time and revision-ease). To use a driving metaphor, it's always a pleasure to take the scenic route, but sometimes you need to get there on time. A healthy mix of both seems the best way to go, if possible.

John J Reiser

In reply to Re: (nrd) Are design patterns worth it? by newrisedesigns
in thread Are design patterns worth it? by FoxtrotUniform

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 about the Monastery: (7)
    As of 2018-05-22 09:08 GMT
    Find Nodes?
      Voting Booth?