3 ms·
Except that Fowler used YAGNI to produce the "Chrysler Comprehensive Compensation System" that FAILED MISERABLY. I still don't understand why people continue t
by bsder 11y ago
Except that Fowler used YAGNI to produce the "Chrysler Comprehensive Compensation System" that FAILED MISERABLY. I still don't understand why people continue to listen to him--he has yet to demonstrate a large project he was in charge of that succeeded.
YAGNI gets you the easy 80%. The problem is that YAGNI means you didn't prepare for the hard 20%, and now you're going to get killed.
Of course, YAGNI is really good if you're an ambitious manager since you'll be gone when the 20% comes home to roost.
- necrodawg 11y agoSuch failures are more often because of bad developers than anything else. It's not really fair to blame a single person on a big project with lots of people on it.
- bsder 11y agoExcept that he is preaching the exact opposite. He is preaching "Follow my religion and your project will succeed! Pay me money to teach you." Given that, it is entirely fair to blame him and his system for the failure. Just so you know: I do agree with you that big projects rarely fail because of a single person. But Fowler pisses me off because he preaches his religion with zero empirical evidence it is any better than anything else.
- necrodawg 11y agoTotally agree :)
- pbowyer 11y ago> But Fowler pisses me off because he preaches his religion with zero empirical evidence it is any better than anything else. And people take it as truth rather than opinion. Look at the way he was all-out in favour of microservices, then backpeddled recently. It's right for a clever man to think out loud and change his mind; but not for people to act on it as if it's fact.
- lmm 11y agoMost C3-like projects fail after a decade and millions of wasted dollars. Failing faster and cheaper provides real value.
- bsder 11y agoExcept that there was already a working system. So, the C3 system was totally wasted money, and never achieved any significant subset of functionality of the old system. A "proper" use of agile would have been to gradually convert chunks of the legacy system to a unit-tested system. Use bug reports and feature requests to prioritize the chunks which need to be tested. Once that happened, you could begin evolving the old system and adding features without worrying about breaking it. But that wouldn't get noticed. Much better to have a BIG, NOTICEABLE failure that you blame others for than a less noticed success. That's how you get promoted, don'tcha know. See: https://en.wikipedia.org/wiki/Putt%27s_Law_and_the_Successful_Technocrat https://en.wikipedia.org/wiki/Putt%27s_Law_and_the_Successfu...