Yep. Unless you are writing a supply chain model that connects into your maintance department and electrical cost centers, in which case you are going to need to use the MyBossHasNoClueWhatHeIsAskingFor pattern.

More OO is all well and good except you eventually reach the point where all you can think in is creating more objects. And then performance goes to absolute Hell. OO in moderation rocks, but very few folks actually understand how to get there.

I know I have aborted (for-fun) projects because of OO design issues. I wanted everything perfect. The solution for me is to not embrace perfection and mix OO where applicable with procedural coding. OO can be used with data units, but there can still be functional/imperative constructs. So far, I'm having a lot more fun.

Professors that teach OO is the only way are really damaging the minds of their students. In some cases, OO solutions are intractible, in others they are great solutions. Chosing when and where to draw the line is the key to Software Design...something 85% (fn 1) of all software architects miss.

--- fn 1. 95.8% of all statistics are made up)

In reply to Re: Re: Light Bulb Joke by flyingmoose
in thread Light Bulb Joke by Cody Pendant

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.