thatraja wrote:
Herebefore I didn't used any of these pattern in my project due to my old employers who are still using outdated concepts
This mania with design patterns is at least mildly retarded. I've used MVC before, because it made sense, I wrote a video jukebox program which used MVC mostly to create an architecture where multiple controllers were supported, because the jukeboxes had a variety of custom input devices, each of which required a controller. No framework, no design pattern, no architecture is going to fit all sizes, with the exception being that any database driven project should have at least three tiers, unless an entity framework is used, and provides that layer of abstraction. The reason all of these patterns exist is in part a mania with patterns as a silver bullet to overcome the various shortcomings of the teams that choose to use them, but it's also in part because of a continued recognition that while various patterns are used often in software, and there's a benefit to naming them, those various patterns all exist as solutions to different problems. As you've said nothing about the nature of the project you're undertaking, it's clear that you don't understand how patterns fit into the scheme of things, or the degree to which they are not a substitute for a good design and good coding practices.
Submit an article or tip