I wouldn't place *too* much stock in the old "function/procedure/subroutine should fit on a screen" canard, because its origin predates OOD--and at least in my experience it's a lot more common for OO subroutines to be verbose without a loss of coherence than it is with other methodologies. A procedure should have a coherent idea, and when it starts to become some sort of swiss-army-snippet, it's probably time to split things up or at least make some subprocedures.

As far as "forseeing the end early" goes, specification is kind of a black art. Part of the reason to do it isn't necessarily that you *can* forsee the end--it gives you a possible end, so that you can then read it and go "oh wait, that's not right at all, it should be this other way". If you don't define things, they tend to be sort of...amorphous as long as they stay in your head, which makes it hard to code them. So I suggest coming up with a semi-complete idea of the end early...not so much to fix the end in place, but to give yourself something concrete to make changes to.

In reply to Re: Looking for help with design philosophy by ssandv
in thread Looking for help with design philosophy by stevieb

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.