By mikeborozdin
via mikeborozdin.com
Published: Jan 05 2010 / 07:36
Design patterns are not a universal tool that can be applied to any project or be used with any programming language. Quality code can be produced without implementing any pattern or even without using OOP. One shouldn’t think of their colleagues as of bad developers if they don’t know the names of fancy design patterns. Moreover, not any single programming project is a business application.
-
IBM bans employees from using Siri over privacy fears
-
Another battle royale: SAN vs. local storage for VDI | ZDNet
-
The Week in Drupal: May 25, 2012
-
What the!? mouse Drag Operation Failed. Could not retrieve schema information
-
Top 10 Cloud Applications for Web Designers and Developers
-
MinuteSort with Flat Datacenter Storage
Comments
cbang replied ago:
No they are more like tracer bullets.
Dave Newton replied ago:
I don't understand what "not every application is a business application" has to do with design patterns, but whatever.
In any case--not knowing about patterns doesn't necessarily make you a *bad* developer, but I'm usually wary of *uneducated* developers. Patterns are ubiquitous, talked about *all* the time, and some of them are so prevalent they're almost everywhere.
Not knowing even the names of some of the most useful, applicable ones (even in "non-business applications" isn't a sufficient condition to call a developer "bad"--but it's a warning flag.
jakyra replied ago:
Not every programmer will figure out design patterns on their own and really, do we all have to reinvent the wheel?
This really strikes me as "now that I know these I find them simplistic." Forgetting his time as a programmer before he used them or how they're useful for people learning programming. Design patterns are a tool, they're a way to teach things that others have learned and facilitate communication. Are they overused? Probably. That doesn't make them bad.
Can we not throw the baby out with the bath water?
Voters For This Link (13)
Voters Against This Link (7)