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

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation. In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can up

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices. Some of the rules  The roles of Scrum • Scrum Master - • Product Owner • Feature Team The PDCA cycle (  )  frequent communication about risks (daily) • Plan – Sprint planning • Do – Actual engineering sprint – deliver a potential shippable code • Check – Sprint review • Act – Retrospective  The scrum guide @ will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum. Apart from these rest of

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