That is interesting, I realize I tend to start from 'make it right, then make it run.' My reasoning for this is that I know how I want my code to look and where I want my values to be so I focus on putting things in the 'right' place. So when I have to go make it run I know where all the problems should be. I not saying that I don't have bugs, gods knows that I ain't true, but at least I should a general idea of where the problem is going to be.

I see too many programs that were written to run first, and never bother going to the second step. The usual explanation being, if it runs, it must be right! :)

In reply to Re^2: what are all the things to be considered to write a effective perl script or module? by Herkum
in thread what are all the things to be considered to write a effective perl script or module? by balakrishnan

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!
  • 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, details, 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, summary, 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.