3 ms·
YAGNI is not an excuse to take lots of shortcuts against known good implementation patterns. Second guessing years of people doing things right by naively assum
by jillesvangurp 4y ago
YAGNI is not an excuse to take lots of shortcuts against known good implementation patterns. Second guessing years of people doing things right by naively assuming you won't need something is more likely to be a mistake than it is not. Do it properly the first time. Actively creating technical debt against your better judgment is silly.
- bazoom42 4y ago> YAGNI is not an excuse to take lots of shortcuts against known good implementation patterns. I’d say it is, because “best practices” and “patterns” are usually context dependent and will have a negative cost when applied when not needed.
- gpderetta 4y agoAbstraction is critical, but it is also very hard. Unneeded and wrong abstraction creates more technical debt than no abstraction. A simpler design is easier to extend, and worst case rewrite, than a more complex, abstract design. If you know by experience, personal or otherwise, that a design or abstraction is sound, and you know you are very likely to need it in the future, go for it. Otherwise, YAGNI.