Hi Monks,

I'm asking for your wisdom. I have a co-worker I have to work with and my job is to assign tasks to him. The problem is I want him to code OOP style and use Template-Toolkit for websites. He refuses to use objects as he is used to programming using numerous 'subs' in the script's code. He says he has no problem adding new functionality or changing something. I showed him some code of mine. Please note everything was in its place, seperate classes for different tasks. Ie one class is to fetch data from our servers. The 2nd class is to parse replies from one of our servers. The 3rd class processes replies. All these classes create a new instance of the 1st one to fetch data. It's all nice and very easy to understand and to add new methods, implement new features. It has nice logging facility (a separate class is used for logging purposes). So, he said he would spend more time programming OOP style than using subs. My answer was and still is to use OOP. I'm sure somebody will have to implement new features in these scripts one day. In my humble opinion, it's much easier to work with a nicely organized code than with a file XXXXX lines long that does all kinds of junk.

And the question is... how can I convince him to start programming OOP style and be organized? I'm just stuck with this guy due to company's reasons. And I want to teach him and make things better in life. I hope you, monks, understand me. I even suggested we write a simple script in OOP and subs styles and then implement extra functionality and see what it feels like to do it in both scripts: his and mine. He disagreed as 'he was not interested in spending his valuable time for such stupid competitions, and classes are damn slow even in C++.' I just can't handle it. I confess. Please help me to find a way to deal with it properly and show him the way to go and make him believe in the power of OOP.
Thank you so much and take care!

In reply to 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.