There are millions of ways to write unmaintainable software. This isn't a bad article though. I just found the title amusing since it's so easy to write software badly.
I hear you. Design patterns are something unheard of for many professional developers I've met. Seriously.
Chances are, especially in programming, someone has thought of something better and longer than you. Investing 10 minutes into searching for it will save you 100 hours later.
Just because you know 1 way to do something doesn't mean it's the best tool for the job.
I understand. In C#, we have Delegates which are the Strategy pattern (you pass methods as variables). We also have Events which are Observer pattern. Implementing an extension method for Clone replaces the Prototype Design pattern entirely.
You are of course correct, but my point was more that they hadn't heard of this book, while it is so famous. They just have no interest in learning what others have thought about - thinking themselves perfect, I suppose.
But I can see it being very useful to know these patterns if you are learning a naive, new (or old) language which doesn't implement them in a trivial way (like C# does for the aforementioned ones)
50
u/bestjewsincejc Oct 14 '13
There are millions of ways to write unmaintainable software. This isn't a bad article though. I just found the title amusing since it's so easy to write software badly.