3 ms·
Yes, it's the 90-90 rule. It has its own Wikipedia entry: https://en.wikipedia.org/wiki/Ninety–ninety_rule https://en.wikipedia.org/wiki/Ninety–ninety_rule "Th
by renegade-otter 3y ago
Yes, it's the 90-90 rule. It has its own Wikipedia entry: https://en.wikipedia.org/wiki/Ninety–ninety_rule https://en.wikipedia.org/wiki/Ninety–ninety_rule
"The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time."
- coolgoose 3y agoI always knew it as the 80/20 rule :D
- mathgeek 3y agoThat’s the Pareto Principle. https://en.m.wikipedia.org/wiki/Pareto_principle https://en.m.wikipedia.org/wiki/Pareto_principle
- mhluongo 3y agoSo is 90/10.
- skeeter2020 3y agoread the thread again; it's the 90/90 rule.
- mathgeek 3y agoThe wikipedia page for the 90/90 rule quite literally says “not to be confused with the 90/10 rule”.
- throw310822 3y agoStrange, I knew a less humorous (and, I think, more useful and realistic) rule: 80% of the work is completed in 20% of the total development time; while the remaining 20% of work consumes 80% of the time. And this is something I've seen again and again: the large, most impactful features and architecture of a system are designed and implemented fairly quickly; it's the many small details get forever to be defined and implemented accurately.
- e12e 3y agoThe 90/90 rule captures the notion that (programming project) estimates are wrong, in addition to the Pareto principle. Now if 90/90 is accurate because of unknown unknowns, or just because we are all terrible at estimation and planning is debatable;)