I wouldn't call testing "training wheels", and I wouldn't compare it to brain rot from using a calculator. Test code makes you think more, in fact.

As for the rest of the stuff, you have to find how you work best, adn do that. Don't necessarily try to copy how someone else works.

For me, I try to create small, compartmentalized code that I can easily test. With small bits, I don't need a big block of time to work on it (more breaks without losing context), can write focussed tests, and can make easier changes. A long hacking session isn't necessarily bad, but if you have to do that to get anything done, you aren't being effective.

--
brian d foy <bdfoy@cpan.org>

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

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.