Re: Are design patterns worth it?

[diakonos]

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!