dhananjaisharma10 / dhananjaisharma10/GoodSoftwarePractices
YAGNI principle example
Open
enhancement
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Write a file in which we have a class with some parameters. Some of the parameters have a foreseeable, but not definite, usage. Write an interface which has currently only one version, but in the future, could have 2 derived classes from it. Demonstrate how that should be avoided using the YAGNI principle, as there is no definite timeline for the second derived class.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.