Be sure to ask him to submit all requests as UML diagrams, in triplicate, with TPS cover sheets and circles and arrows and a diagram on the back of each one.

Thanks for the recommendation. I'm really well-served on bureaucracy, believe me. The client have a CMM L2 certification and all projects must fulfill a lot of bureaucratic requirements. :-(

On the other hand, if you want to keep your job, maybe digging a little deeper is the way to go here. Maybe your architect knows what he's doing. Maybe he has solid, concrete reasons for asking you to do this.

Not really. He have a Java based mindset, just that. It's not his fault, he actually works with Java. perrin and izut arguments are enough to convince him about the non-need of VOs for implement a good DAO in Perl.

The Lucene and Plucene examples

Thanks for those. They were nice and very illustrative. It started to show the light to my poor architect. :-) May the gods bless you for this example and him for accepting it as a good starting point.

And the Java guys would rightfully snear and make posts very similar to yours.

Oh, please! I'm not sneaking. I'm posting this with the agreement of my architect. We are good friends, and both of us are having fun with this project. :-)

BTW, thank you very much for you point of view, it was quite useful. And thanks to perrin and izut for pointing good solutions for avoid extra coding and still having high quality Perl code.

-- monsieur_champs

In reply to Re^2: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by monsieur_champs
in thread Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by monsieur_champs

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.