Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I find myself breaking this pattern all the time.
YAGNI – You Ain’t Gonna Need It
I am only a Junior Developer, but I find even Senior level developers doing the same thing.
“Well, this system might use it, and this one, so let’s design for it.”
Sometimes, I catch myself, but most times I run wild. Does anyone have any tips for sticking to YAGNI, or anything I can do to better enforce this design pattern while I am designing and coding?
Designing FOR something
…is completely different than
Designing something.
Designing for something means you’re architecting your application for future expansion in case the need arises to write the code (which is good…it means you’re making your software extendable and easy to maintain).
Designing something means you’re writing the whole piece now…whether you think anybody is actually going to use it or not. That isn’t necessarily a bad thing, but it can be a huge waste of time.
Be careful about which one you’re doing.