If a problem occurs over and over again, a solution to that problem has been used effectively. That solution is described as a pattern. SO design patterns are not like something implementing the simple logic.Its already been developed to solve the complex problems.Design patters has its own place untill and unless you dont have any alternate solution to the specific complex problem related to that design patterns.
By
dinkar v kolhe, Software Developer, Apsora pvt ltd
| 03 10 2010 10:57:57 +0000
Agree with Krishna here. The frameworks were developed based on several observed design/usage patterns. During the earlier application design, the design patterns have been used/applied knowingly/unknowingly (based on experience). People like GoF(Gang of Four) have brought these patterns to our notice and enabled the usage/application of these patterns knowingly in suitable places and with lot more confidence and belief.
By
Tulshekar Gangireddy, Engineering Manager, Akamai Technologies India
| 01 11 2010 06:23:23 +0000
Design patterns are very important for any type of prgramming. By using Design patterns coding becomes very easy and also help to find out where is your application is stucking...
By
viral modi, Software Developer, Yash Technologies
| 04 09 2009 05:16:02 +0000
Absolutely right firas,Recurring problems are the order of the day in
both the real world as well as the software world. In the software
world, the solutions for these problems are known as Design Patterns. J2EE is no exception. And since J2EE promotes tier-based development, each tier has its own well defined Design Patterns
By
Radhakrishna Marar, Business Analyst, Oracle
| 03 24 2009 04:45:00 +0000
Design Pattern is a proven design for a problem/scenario recognised by developers. Instead of you designing something not proven to be best and doing a trial, it's always best to go with what have been recognised the standard, best, efficient, reusable, fastest way of solving your requierement.
Hence in any sphere of Programming Language Design Patterns are a must, and one can't live without them.
By
Anant Agarwal, R & D Engineer, Synopsys (India) Private Limited
| 03 22 2009 11:49:15 +0000
Design patterns are mandatory not only for open source applications allowing developers to contribute but also for commercial software in terms of team work, sustainable product and upgrade.
By
Firas Mkaouar, Software Developer, ADHOC
| 03 02 2009 09:26:35 +0000
In a way most of the frameworks internally are based on design patterns, and there are scenarios which can be handled well by using a pattern even if one is using a framework. So, I think we should take decision to favor a design pattern or a framework based on a particular situation. Ruling out design patterns is certainly not a good idea.
By
Saket Vishal, Sr Consultant, Xebia
| 08 12 2008 21:03:10 +0000
Employing Design patterns in an application is an eleganat way of coding.Design pattern eases the developers scope of problem soovling, given a problem the developer has to just think on which design pattern would solve it. Frameworks are useful but they cannot replace design paaterns as framworks alone do not solve the Clients business needs.
By
Ignatius , Technical Support Manager xxxx
| 08 12 2008 16:42:03 +0000
this is impotent to Accept and apply Regulation of Design Pattern as they are already proven. yet if any problem exist with system that can be solved separately. Regards Brajesh Yadav
By
Brajesh Kumar Yadav, Software Developer Appnetix
| 08 11 2008 21:41:33 +0000
Though there are many open source framework present but sometimes due to the complexity of the project only design pattern could be helpful.
By
Jitena Bhansali, Business Analyst, SAP
| 08 05 2008 07:25:06 +0000
|
Yes I support Shashi Prasad. For all those argue for design pattern i have a simple question. How many times have you mentioned a pattern name in your design documents? or any other project documents. In my case it is none. In contrast we always mention the frameworks and technologies. The frame works we use more or less represent the patterns we are going to use. For eq: Struts => MVC + VO , Spring => IOC + VO + DAO , JEE6 => CDI When we have to solve a problem or a common problem the best approach is to refer documentation/advice from respective framework/community. We never use design pattern approach aka. study problem , then search for a design pattern, and then apply the design pattern. Although i am not in favour of heavy documentation , it is surprising to see people support the terminology which they never use in their day to day work. For me design patterns just remain as a over used buzz word which is useful only for HR managers who like to flaunt their technical know how.
By
Vijay Kumar, Service Delivery Leader, Nucleus Software Exports
| 05 16 2010 02:54:48 +0000
|