I used to, this way gives me three advantages.

1. I tend to work more efficantly when I can stay on track -- If I have an idea how to improve something and get side tracked on fixing a bug that just poped in the code then I take a while to get back into the flow once I fix it. If my bugs were usually severe and requiring a complete redesign this would be moot.

2. If I do implement solution X, and in the middle of implementation I figure out that solution Y is better for whatever reason I have many stop points I can jump back to implement solution Y.

3. I can audit my code almost change by change and show movment.

-Waswas

In reply to Re: Re^3: Test output: Interpret or pass/fail by waswas-fng
in thread Test output: Interpret or pass/fail by mandog

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.