Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Design patterns can be a good thing. Especially when working in a fast paced project group. Many times (Shall I say most all the time) the code you create today is the same code someone else changes tomorrow. Without some sort of "known structure" (not intense design patterns) that all have painfully tried to follow it can become difficult. To me the reason for this is quite simple. After everyone in a project group learns a specific "structure" then modifications become quicker and easier.

That said, I think there is one more area that holds more importance than having a set structure. DOCUMENT, DOCUMENT, DOCUMENT. (Have you ever tried to quickly figure out a two line regex? - "Man those comments are nice")

You will see a lot of different code in your lifetime. I believe that a person's code is similar to their fingerprint. In project groups now and in the past I can always tell who wrote the code without looking at their signature on the header comment lines.

Don't sweat it if your code doesn't "look like the rest". But if you use design patterns don't let it destroy your code (making it more complicated than it should be). I don't scream when I run into the "BIG BALL OF MUD". Actually much of mine has been named as such.

Have a great day!

In reply to Re: Are design patterns worth it? by diakonos
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
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (4)
    As of 2018-05-27 21:51 GMT
    Find Nodes?
      Voting Booth?