3 ms·
Or unless those "other things" have unlikely but potentially really bad consequences. Most of the time, maybe 80% of the time avionics software does not need t
by ams6110 17y ago
Or unless those "other things" have unlikely but potentially really bad consequences.
Most of the time, maybe 80% of the time avionics software does not need to contend with the plane flying through a thunderstorm. But I hope that the programmers didn't just toss that possibility into the "not important" category.
The "80/20" rule is something MBA types like to toss out so that they sound wise, but in some cases it's needs to be more like the 99.80/00.20 rule.
- runevault 17y agoWhen working with code that's effort has lives on the line, the rules obviously change entirely. How many people ACTUALLY work on such systems though? For the majority the 80/20 rule is going to be fairly legit a large portion of the time.
- cema 17y agoThe 80/20 rule is self-applicable and so applies to 80% of cases. (Captain Obvious said hi.)
- cema 17y agoIf the "80" here is reasonably accurate, then here is what we have: in 80% of the cases, we only have to focus on 80% of stuff (that's about 64% of the total), and in the rest 20% we focus almost on 100% of stuff (that's almost 20% of the total), which means that we need to focus on almost 64+20=84% of the total, which is still pretty close to the original 80%. :-) OK, this is silly. (We can only get it equal when we go with 100% instead of 80%.)