> Educate, supervise, mentor and pay a developer more and they will be more careful.

Having already problems to find skilled personnel, a manager will think twice to pay more!

Especially if his competitors can solve more problems with less and cheaper hackers, just because they are guided by a strict framework / IDE.

Then he will rather try to imitate their approach.

> That's the nanny-state of programming.

So you are never activating strictures, because you don't want to be "nannied"?

Maybe time to return to assembler? ;)

> Aesthetically, at least, I am not comfortable with the "has" and friends.

Saying so I'm critical about has because it's putting the emphasis on the objects data during the design process.

An object is primarily doing something it's not necessarily supposed to have something.

It should be planned by its interface not by its state. °

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

update

°) See also this excellent talk

"Tadeusz Sośnierz. How Moose made me a bad OO programmer" on YouTube

Tadeusz is showing how syntax decisions are nudging programmers into designing objects leaking their internal state instead of hiding the implementation.

In reply to Re^7: oop, variable that counts the number of objects created (updated) by LanX
in thread oop, variable that counts the number of objects created by Anonymous Monk

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.