4 ms·
YAGNI is not about things you know you need, because then you wouldn’t write any code ever.
by bazoom42 4mo ago
YAGNI is not about things you know you need, because then you wouldn’t write any code ever.
- Scubabear68 4mo agoThis was the issue with the early agile-developed systems. Not that they didn’t write no code, obviously, but they didn’t understand the domain and so YAGNI’d everyone to death. As a result there wasn’t enough code for the system would do what it needed to do. The code was simple and highly testable, but didn’t actually do the job.
- bazoom42 4mo agoAre you referring to some particular projects, or to the early stages of every project?
- Scubabear68 3mo agoThe original Agile poster child, Chrysler Comprehensive Compensation System (C3) was never very successful as a project. It achieved only a fraction of its goals and was ultimately cancelled. YAGNI in that context is hilarious, because they were replacing an existing COBOL based payroll system. They literally needed pretty much everything the old system did to be successful. Part of the failure is because the devs did not understand what they were replacing.
- bazoom42 3mo agoAh, that sounds like a classic mistake - rewriting a system from scratch without fully understanding what the system actually does.