Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I studied C++ and the GoF book long before i embarked upon the Perl path. At some point during my journey down the Perl path, i thought it would be really neat if someone (me) wrote Perl versions of each of the GoF Patterns. Well, someone already did (partially) - But, there is a funny thing about Perl - read Dominus's "Design Patterns" Aren't for more.

I personally think that Design Patterns are worthy of studying, they can really help you design better. There are real world examples of Design Patterns implemented in Perl, such as what Matts discusses at his paper on Proxy Objects. There are plenty of other examples here at this site, such as a Factory Pattern that i demonstrated a while back (be sure and read Kanji's and merlyn's comments from the root thread as well if you do follow that link). Just try the new and improved Super Search (tye++ once again).

Now, are Design Patterns going to reverse the Big Ball of Mud for you. No, only you, your co-workers, a lot of planning, and time can do that, but that doesn't mean that you shouldn't learn how a few patterns work. You never know when they might be useful. I wish you the best of luck, i myself have been handed a medium sized ball of mud (written in ASP and VBA for Access, no less) that someone else wrote. Right now, the most critical piece to shaping this lump into a more manageable product is to clean up the database schema - to bad the GoF didn't invent a Preventative LART Pattern*. I can't complain though, it is nice to be employed again. :)


* prevents non-coders from thinking they can

In reply to (jeffa) Re: Are design patterns worth it? by jeffa
in thread Are design patterns worth it? by FoxtrotUniform

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    NodeReaper silently materializes above an unsuspecting visitor

    How do I use this? | Other CB clients
    Other Users?
    Others about the Monastery: (4)
    As of 2018-05-25 05:55 GMT
    Find Nodes?
      Voting Booth?