I have been using an approach similar, breaking tasks down into chunks (subs) and also writing the interface to a module before coding the module. Yes, I am also trawling through CPAN so I don't reinvent the wheel. These things I feel are working reasonably well for me.

However.....I'm still finding that halfway through the coding I'm either having that 'lightbulb' moment and scraping half the code and starting again or , as I mentioned in my original post, I code myself into a corner...usually with unwieldy data structures that get more out of hand as I progress.

Maybe I need to 'play' with my sub templates a bit longer before I start fleshing them out with the actual code?

In reply to Re^2: Perl Software Design Process by TeraMarv
in thread Perl Software Design Process by TeraMarv

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.