My basic philosophy of programming is that if I have to do something more than once I'm going to put it in a module or a library or a library of modules and never write it again. This in essence is where OO programming enters the picture.

If you can create a base of good objects that you can re-use and keep stable you save yourself a lot of work later on. Not only that if you have written your modules correctly and in a concise fashion anybody else that has to maintain your code will be able to understand what you did in the first place.

At my current consulting assignment there are two basic classes of code that I have had to deal with here. There is the stuff that was written in an OO style and the legacy stuff.

When a defect is reported in the OO stuff I can usually track the problem down in a manner of minutes. If the legacy stuff breaks, and it does often, I can be chasing my way around the code for days trying to find a problem.

Get by? I'm not sure what that means to you but I'm not sure that getting by is acceptable... 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Peter L. Berghold --- Peter@Berghold.Net
"Those who fail to learn from history are condemned to repeat it."

In reply to Re: Should I learn OO programming? by blue_cowdawg
in thread Should I learn OO programming? by nysus

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.