3 ms·
> YAGNI isn’t a rule, it’s a dismissal. A dodge. A cop-out. No, not really. YAGNI is about making it clear that you do not need to waste time putting together
by rualca 5y ago
> YAGNI isn’t a rule, it’s a dismissal. A dodge. A cop-out.
No, not really. YAGNI is about making it clear that you do not need to waste time putting together abstractions that aren't required to implement anything, and are nothing more than nice-to-haves that increase complexity but buy you nothing.
At best, YAGNI is a tradeoffs between the risk of piling up tech debt (and typically a very low risk) and improving the maintainability of your code base (because you avoid piling up cruft that you do not need).
- hinkley 5y agoThat's what it was supposed to be for, 20 years ago when it was introduced to the wider world. That's not how it gets used most of the time now. It is rare that I hear someone use it the way it was meant to be used.
- rualca 5y ago> That's what it was supposed to be for, 20 years ago when it was introduced to the wider world. That's what YAGNI still is and always was. It never changed. At all. Another thing that never changed are those who criticize YAGNI because they feel the abstraction they wish to add is somehow a must when it really isn't.