The YAGNI programming principle
The programming principle YAGNI (You aren't gonna need it) assumes the rejection of excess functionality in the system you are developing, i.e. if there is no immediate need for a task or method, then you should abandon them.
When planning your project, following the YAGNI principle, you should not write code that you might need someday, but instead focus on solving the most pressing and important tasks first.
See also
-
principle
SOLID,
which sets guidelines for OOP-based software -
principle
DRY,
which is the division of software into small components -
principle
KISS,
which involves abandoning the complication of software -
principle
CQS,
which specifies only one command for each function -
principle
LoD,
which is used in software development -
responsibility separation principle,
which is used in software development
