Of Design patterns & Software Engineering

Well...perhaps am the wrong person to write about this. Or perhaps I am the right person to write about this....:D....so much for being a software engineer. How can I not write about Software (atleast once in a while)...?

Anytime, u read/refresh GoF(it's not Harry Potter & the Goblet of Fire but the Gang of Four I am referring to) design patterns(that sort of shows I have been reading of late...no prizes for guessing this :D) you wonder if this is only a piece of common sense or something more great?

Common sense because most of it looks simple enough but great because of the comprehensiveness & completeness associated. Imagine yourself assigned the task of identifying the mosty commonly used software tasks so that those tasks can be built for reuse. Given that the design patterns has become pretty much popular, it sounds simpler...doesn't it? I am sure, I would have come up with a bunch of things......more than what GoF suggests or club many of them together, say get away with the Abstract Factory, so on & so forth. Not sure if mine would have been exhaustive. Well that's what distinguishes me from them..........:)

Perhaps what is great about design patterns is not just knowing them but using them as a matter of practice. Using them in the sense of building code/modules in real life based on those.
Most of the people I met used a couple , may be few but none till now who built all those. No brickbats blaming my circle for this......and once again Hail GoF!!