I wonder about your working style. From your problem, I would like to suggest following approach.
1) It seems that you don't have any coding standards in place, please prepare them and approve them from Top management.
2) Always ask programmers to create a 'Design report', before he/she touches the code, carry out the practice of 'Design review' by some unbiased 'Senior' programmer (Not you, since you already have conflict with the said guy)
3) Always remember that OOP is Not always right approach and hence in case of any conflict, call up a meeting with Senior Programmers and both of you, and come to some conclusion at the end of the meeting.
4) DO NOT Force programmer to write code if he is Not okay with your design, simply because he would Not give you good output. In that case change the programmer.

In reply to Re: Coding styles: OOP vs. Subs by sanPerl
in thread Coding styles: OOP vs. Subs by nikos

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.