Skip to main content

Why do we need a design pattern? Some FAQ's

Why do we need pattern? cant we just code?
Well we need it for ourselves. It just like constructing a new house and you go to some engineer for the blueprint. Nobody stops you from creating your house but most of us will take the advice of the people who has sufficient knowledge in this area.

Similarly a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. It is template, industry best practice, a tested solution.

when should i start thinking about patterns?

You should think about the patterns the moment you start thinking about the new project. Typically you should have a foundation of the application before you start coding.

Is it worth spending so much time for so called "designing patterns"?
I have found many projects worrying about performance, tight coupling, re-factoring code, difficulty in adding anew modules ... endless complaints when the project goes live or nearing completion. At this critical juncture companies spend millions for fine tuning the application. All this could have been avoided if a proper though on the architecture was given before the coding commenced. Don't think that only naive developers make mistake. I have seen experienced developers working in CMMI5 level companies making such mistakes. Many times even i was forced to do such things because of "pressure".  This has to be thought by all the stake holders. 
A properly designed application wont give us last minute surprises. so i strongly advice to create a strong design pattern before you start

Practically How can it help me?
Design patterns can speed up the development process by providing tested, proven development paradigms. Effective software design requires considering issues that may not become visible until later in the implementation. Reusing design patterns helps to prevent subtle issues that can cause major problems, and it also improves code readability for coders and architects who are familiar with the patterns.

Is it a silver-bullet for all my problems?
It wont solve all the problems which you may face, but it will surely provide you the tools and insight by which you can face & solve you problems. It is better to be prepared than feel sorry later.


Popular posts from this blog

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed. Plan  This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team. DO Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process. Check Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down. ACT If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I

Why is potentially shippable product quality important

Agile teams work in iterations. During this period, they are supposed to work on product increments which can be “delivered” at the end of iteration. But how you know that the correct product was delivered? Many teams have different kinds of acceptance criteria and Definition of Done (DoD). But in many cases, this “done” is not the real “done” there might be some testing pending, some integration or review pending or anything else which prevents the actual use of the product increment. Many of these teams will need additional iterations to finish hardening their products. Many teams will implement different types of “gates” or approval steps to move to next stage. The free flow of product will be interrupted. They might end up doing mini waterfall within their agile process. Many don’t even realize this. This results in poor quality and requires additional effort to “harden” the product. Potentially Shippable Product increment The acceptance criteria and DoD should be modified