I was really surprised when I heard a number of people saying “Patterns suck”, I wanted to find out why some individuals hate these precious guidelines which save us from reinventing the wheel and lets us make use of it.
Fortunately after just 7 days I had to cooperate with some confident people, often proves to be pattern-lovers. Having a lots of technical knowledge, they remembered names of patterns and writers on finger tips. People, you are able to speak techno babble with for not just hours but also for days. In the first place I admired them and discovered myself among knowledgeable people.
Then I found something strange, besides all of their knowledge that they had very few accounts of success and the management hasn’t been satisfied with their problem solving skills.
I had started observing what causes their failure. Mean while I were forced to design an architecture for any coming enterprise project. I started scaffolding by enhancing and optimizing my legacy libraries and framework with my team. I asked these folks to review my strategy to let my approach become foolproof.
Geeks love technicalities so I got a prompt response plus they started highlighting the weaknesses, I was very glad as I got to be able to improve. But unexpectedly almost all of the issues identified are highlighted below:
Geek: Aren’t you using NHibernate?
Me: Nope, I preferred these libraries because they are recommended by technology vendor and I found these performent because of this kind of data driven applications. Another reason is our management shouldn’t use NHibernate because unfortunately we cannot have a single hands-on resource neither we have now time with the feasibility study.
Geek: What? Do you know where NHibernate originated in, it is a port of Hibernate, getting used in the most robust language like Java therefore you know .Net has nothing to contend with Jave.
Me: Yes, I agree that Jave this is platforms are much more complex more mature but every language or technology has many of its own specifications and advantages. Our framework and libraries are optimized together with the objects supplied with .Net. Our wrapper classes exploiting a new features provided inside the current version of .Net.
Geek: Don’t use ADO objects, these objects are mess.
Me: Why?
Geek: Because these are certainly not open-sourced neither the approach is pure object oriented, this is why we never rowset in Jave.
Me: I admire the main advantages of open source however these object are rich, free, built-in, tested and performing well in enterprise applications. I do not usually use them but I found them handy in such style of applications
Geek: You incorrectly applied this pattern; permit me to show you the documentation.
Me: This pattern like other patterns have different applications, I am next approach given it performs well on this scenario. This flexibility is additionally allowed by some experts.
Geek: No, patterns ought to be followed along with. They aren’t to be changed for performance or whatever. And remember enterprise applications, built on great technologies like EJB, looks graceful whether or not they usually are not enough performant.
Geek: Increase your variety of layers like we now have did as application. You have not decoupled enough.
Me: Yes previously I do have the same quantity of layers but I thought it was as an overkill so I modified this framework for medium-sized performance-hungry applications.
Geek: And why have you coupled those two major tiers, it is deemed an unacceptable violation of N-Tier Architecture
Me: No, these are typically still two different layers, but I am keeping them in a single project during development as almost all of the developers will work on both layers. They still could be deployed on different servers.
Geek: I’m still unsatisfied, it’s not recommended by our gurus and now we follow them because we all know they are the very best.
Me: They might have recommended it for most different style of project and also this approach might be suitable in this particular scenario.
Geek: We found their practices the most effective in all type and size of projects, whatever, it isn’t that simple you believe it is, you will need to add a much bigger.
… and ultimately I got the reply to my question “why people hate patterns?”
Seasoned Microsoft Certified Professional having in excess of seven numerous years of experience in analysis, design, and growth of enterprise applications; utilizing true world-class software development patterns & practices.