Software Design Principles DRY, KISS, YAGNI

In this article, I am going to explore software design principles and their benefits and why design principles are useful for us and how to implement them in our daily programming. We will see DRY, KISS, and YAGNI software design principles.

We will discuss -

DRY PRINCIPLE - DON’T REPEAT YOURSELF

We will see,

DRY stands for DON’T REPEAT YOURSELF and is a basic principle of software development, aimed to reducing repetition of information. The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, representation within a system “. Reference wiki here: DRYwiki

Violations of DRY: "we enjoy typing" or "waste everyone's time “.

How to Achieve

To achieve, divide your system into pieces. Don’t write lengthy methods, divide logic into smaller reusable pieces as much as possible and try to use the existing piece in your method.

Good example for DRY principle,

Enterprise libraries, helper class, every piece of code is unique in the libraries and helper classes.

KISS - KEEP IT SIMPLE STUPID

A big guy said: The programming language is for humans to understand, computers can only understand 0 1, so keep coding simple and straight, which should be easily understandable by human beings.

Keep your methods small, each method should never be more than 40-50 lines.

Each method should only solve one small problem, not many use cases. If you have a lot of conditions in the method, break these out into smaller methods. It will not only be easier to read and maintain but also can find bugs a lot faster.

There are two codes shown below, both methods are doing the same thing,