Well, you really have answered your own question. You must find the sweet-spot.

Let's start with one end of the continuum: no 'helper' routines. We all should agreee that that's just not a good idea. To a certain extent all functions fit this definition. Sometimes they're tiny, and sometimes they're complex, but any time you call another piece of code, you're reusing it, and the programmer calling it might not understand how it works. Sometimes that's OK. I use stuff from CPAN that I don't understand, but to a certain extent, that's the point. I don't have to understand, I don't need to understand, I don't even *want* to understand.

At the other end we have the old cargo cult phenomenon. It's real easy to be bad-lazy and reuse code in the wrong way, or in a very inefficient way. I think this is where experience is important. A senior programmer can look over a juniors work and make sure that they're not drifting too far into the weeds and at the same time, they understand the pertinent parts of the project.

I work alone, and this lack of peer review (formal and informal both) is without a doubt the single largest drag on my effectiveness and productivity. So, good luck, and make sure to have seniors and juniors working together.

In reply to Re: Helpers Vs. Hurters by pboin
in thread Helpers Vs. Hurters by BaldPenguin

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.