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

comment on

( [id://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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2024-04-19 11:54 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found