Factory Method is known as a creational pattern. As the term present it is used to create something. To create objects such that it kept decoupled from implementor. It is as simple as creator should hide the creation of object to others. Hence, any future changes in the object should not impact implementor. “Don’t let […]
An JSTL Tag Library with descriptive image for better understanding. Keep it in mobile, tablet, laptop to be productive. Set it as your desktop background.
An SQL Joins with descriptive image for better understanding. Keep it in mobile, tablet, laptop to be productive. Set it as your desktop background.
An HTML5 Elements with descriptive image for better understanding. Keep it in mobile, tablet, laptop to be productive. Set it as your desktop background.
Like our markdown linters, all Mapbox documentation repositories use a shared ESLint configuration. Our configuration covers everything from enforcing React best practices to improving accessibility, including: eslint-config-mapbox is a shared ESLint config for Mapbox engineering teams which serves as the base for our configuration. eslint-plugin-react includes React specific linting rules. eslint-plugin-jsx-a11y checks accessibility rules on […]
The CSS Paint API (part of the magical Houdini family) opens the door to an exciting new world of design in CSS. Using the Paint API, we can create custom shapes, intricate patterns, and beautiful animations — all with a touch of randomness — in a way that is portable, fast, and responsive. We are […]
Open Closed Principle: In short, Open Closed Principle tells us “You should not modify existing behavior but if you want, you can extend it according to your needs.” i.e. Code is open for extension but closed for modification. Example: Consider we have a Vehicle class and a Mechanic class. A mechanic can service all vehicles. You are the owner of […]
Don’t Repeat Yourself Don’t repeat yourself design principle is about abstracting out common code and putting it in a single location. It discourages repetitive code. It is about putting one requirement at one piece only. It helps us avoid maintenance jargon. Let us see Don’t repeat yourself principle in an example. Consider a Mechanic class […]
Single Responsibility Principle: It states that every object in your system should have a single responsibility and objects services should be focused on carrying out single task well. Consider we have a Bike class and all the methods associated with bike class as below. At first sight, all the methods seem placed properly in the Bike class. After all […]
Liskov Substitution Principle states that Subtypes must be substitutable for their base classes. At first it does not seem like very difficult to understand. We know that derived classes and base classes talk about inheritance. Yes, Liskov Substitution Principle is about inheritance, but about well designed inheritance. You should be able to substitute subclass object for […]