Join the DZone community and get the full member experience.Join For Free
Bugsnag monitors application stability, so you can make data-driven decisions on whether you should be building new features, or fixing bugs. Learn more.
What Is a Pattern?
Why Use Patterns in Your Applications?
It's when you move beyond the simple and rough snippets of jQuery and start working on the more complex User Interactions that your code can become difficult to understand and to debug.
Patterns provide solid approaches to solving issues you may run into in software development.
Like we said, patterns are reusable solutions that can be adapted to suit your needs, hence they make the application more robust.
Reusing patterns assists in preventing the minor issues that can cause the major problems in the application development process.
Patterns are generalized solutions to a problem. So the generalized approach means that regardless of the application, the Desing pattern can be applied to improve the structure of your code.
If you are reusing the code or solution, naturally, it's going to reduce the file size.
"The secret to building large apps is never build large apps. Break your applications into small pieces. Then, assemble those testable, bite-sized pieces into your big application." -
Is a Pattern a Template?
Yes, patterns are not the exact solution to some problem. They are a template. Thus, the role of a pattern is to provide the solution scheme.
The Rule Of Three
The Rule of Three stands for the requirements for a pattern to be valid. The three key areas that are referred to in the Rule of Three are:
Fitness of Purpose.
Object Literal Design Pattern.
Constructors With Prototypes.
The Revealing Module Pattern.
The Singleton Pattern.
Published at DZone with permission of Puneet Sharma , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.