Quote:
Originally Posted by Kolenka
If only regular people know how many known issues most software tends to ship with (when there is a sizable QA/test org). They'd probably either drop their jaw or complain even more loudly. One of the factors used when deciding to fix a bug is: how likely is it that someone will hit it? Bugs with a higher likelihood of being hit will get fixed first. Or bugs that do bad things like crash the device, delete data, etc...
|
Yep... that is part of the key to the whole 37 Signals concept of developing error free and usable software. Their concept is that complexity is what introduces bugs. Most software gets away from the core features that everyone needs adding option on top of option. The higher the complexity of the software the higher the bug count goes.
I read an article they wrote about this... and how the PMs of the products reject most user feature requests because it just isn't relevant to either the core reason for the app to exist or not relevant to the majority of users.
BOb