Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Do you lock yourself in a room and code till you finish, or do you ensure you have plenty of distractions in the way of cats and music and family, etc.?
Distractions? What for?
Do you go at it in one shot without getting up, or do you break it up into small phases?
And, most important, do you test as you go, or have you become so good that you don't make silly little mistakes such as misplacing punctuation and the like?
Test as you go by creating test scenarios to verify desired output. If you perceive that you would be wise to become more aware of the perils of punctuation in Perl programming, it is advisable to do so.
How do you write a lot of code while making sure that each smaller component piece is bullet-proof?
In practical application, the method of "test-driven" programming or whatever you want to call it is just the way you end up doing it when it has to get done.   To help figure out "what's right for you", ask yourself:   Would you compose a symphony (or even try to figure out how to play some catchy tune) without picking up an instrument to see if you're on the right track?

<reggae>The wise man build his house on the rock; the foolish man build his house on the sand </reggae> :-)

In reply to Re: Programming strategy with no on-going testing by nerfherder
in thread Programming strategy with no on-going testing by punkish

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

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

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (4)
As of 2021-10-18 06:49 GMT
Find Nodes?
    Voting Booth?
    My first memorable Perl project was:

    Results (72 votes). Check out past polls.