Personally, I find that the most helpful thing when I am maintaining a "complex script" is to have a block of comments detailing the program input structure(s) and the expected output structure. Once you know where you start and where you want to go, the path becomes luminously clear. There is a line from Fred Brooks's (The Mythical Man Month) to the effect that flow charts are pretty pictures, but to understand what the code does, show me the tables. (My copy of MMM is in storage at the moment, so I am paraphrasing from leaky memory.)

----
I Go Back to Sleep, Now.

OGB

In reply to Re: Tool used by Perl developers to design the flow of Perl Projects by Old_Gray_Bear
in thread Tool used by Perl developers to design the flow of Perl Projects by paragkalra

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.