Design Patterns
-
Sometimes, when I read pattern definitions, I can imagine the author/s sitting there going how can we make this reasonably simple idea that's been around for years and years in various forms sound really, really smart and, at the same time, give it a really funky name like 'The Strategy Pattern' or 'The Chain of Responsibility Pattern'? Or how can we make this pile of nonsensical verbiage sound as if it actually does something meaningful? Don't get me wrong; I rather like patterns or, at least, some of them. I just find it amusing that some basic ideas suddenly get popular because they get a groovy makeover.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
It's all about human herd instinct. Make it fashionable, and the herd will flock to it. I've sifted through hundreds of thousands of lines of code lately (maybe last three months or so), and have yet to see a sound strategy implementation. Which is why it's (IMO) still important that patterns get advertised - there seems to be a huge spread in how well prepared programmers are, a lot larger than in the professional knowledge in other domains.
-
Sometimes, when I read pattern definitions, I can imagine the author/s sitting there going how can we make this reasonably simple idea that's been around for years and years in various forms sound really, really smart and, at the same time, give it a really funky name like 'The Strategy Pattern' or 'The Chain of Responsibility Pattern'? Or how can we make this pile of nonsensical verbiage sound as if it actually does something meaningful? Don't get me wrong; I rather like patterns or, at least, some of them. I just find it amusing that some basic ideas suddenly get popular because they get a groovy makeover.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
Astonishing ! I've recently attended a couple of interviews where I was asked about design patterns, so yesterday, I thought maybe I hould read up on them a little. I came to just about the same conclusions. Surely, it's more or less just common sense to someone who's done a bit of programming.
-
Don't ask me there is only one pattern I full understand. Drink Beer, Drink Spirits, Drink More Beer, Drink More Spririts........fall over.....go home. :)
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
Sometimes, when I read pattern definitions, I can imagine the author/s sitting there going how can we make this reasonably simple idea that's been around for years and years in various forms sound really, really smart and, at the same time, give it a really funky name like 'The Strategy Pattern' or 'The Chain of Responsibility Pattern'? Or how can we make this pile of nonsensical verbiage sound as if it actually does something meaningful? Don't get me wrong; I rather like patterns or, at least, some of them. I just find it amusing that some basic ideas suddenly get popular because they get a groovy makeover.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
Yeah. At the time that GoF book came out, I was totally confused by all those crazy pattern buzzwords that were flying about. Until I had some external have a look at my software design to get some feedback and he told me that "yeah, that's the observer pattern alright, and thats the watchamaycallit pattern I recognise over there... looks fine to me." That was the point when I realized I didn't miss anything at all - except the funky new names. Now I do wonder why it took four people just to invent new names for stuff that has been around for decades! :confused: