These are the sorts of things I'm looking for:

* You can write code that simply won't work if it's misused.
* You can write Code with pluggable log points and business logic that becomes easy to test and manipulate with configuration instead of code hacks.
* ... allow you to write code boldly and quickly because you'll have the baseline correct behavior known.

As for test driven development, we are moving towards that. In fact I am co-pointing that study group. One of my basic precepts is going to be: If there's not a test for it, that code shouldn't exist. So if you write your own accessors, you need to write test for all your accessors. OTOH, if something like Moose is setting up your accessors in declarative style, then it becomes a question of: is Moose correct? Unfortunately, getting to the place of test-driven development, is going to be a very long road--we have 7 different systems, and hardly any shared code between them. On top of which, time for developing tests is allocated along with the time needed for bugfixes and adding new functionality.

In reply to Re^2: Help me avoid writing C Programs in Perl for a living by cleverett
in thread Help me avoid writing C Programs in Perl for a living by cleverett

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.