In this article, We are going to study the “YAGNI” software design principle’s benefits and why this principle is helpful for us. Some best principles are KISS, SOLID, DRY/DIE, and YAGNI software perspective.
- KISS [Keep it simple, Stupid!]
- SOLID
- DRY/DIE [Don’t Repeat Yourself / Duplication is Evil]
- YAGNI [You aren’t gonna need it]
Let’s explore YAGNI [You aren’t gonna need it]
As we can read in heading YAGNI stands for You aren’t gonna need it. This principle simply means you don’t need to add any line of code/ any functionality that you need in the future. Just do code for the current situation leave the future things. if you think it will need this code in the future, write in the future. This principle is normally used in the Agile software development process.
As per your thinking, you developed future thing and if for some reason it will not need, all efforts are wasted as well as time and cost also affected.
As we can see in the above image for single future functionality we can face too many issues that affect overall factors.
So I suggest while writing any line of code or perform a task keep this principle in mind and use it wisely. I’ll come with other principles soon.
hope you guys found something useful. Please give your valuable feedback/comments/questions about this article. Please let me know how you like and understand this article and how I could improve it.
