Comment Two words: Spec Compliance (Score 1) 227
If software development is in a commercial context, then making it bulletproof is going to happen in proportion to that being a requirement.
For example
- Your likely customers know the difference and will pay more to get a robust product rather than a fragile one.
- Internal standards mandate bulletproofing, at least against Oopses that will get your ass sued, even more strongly than the urge to get the product shipped this quarter.
- External standards like the software Underwriters' Lab under discussion become well enough known that Joe Consumer demands the seal of approval even if he doesn't know what it involves.
But if bulletproofing isn't in the spec it's unlikely to happen. And as a side note, the acceptance test is the spec.
For example
- Your likely customers know the difference and will pay more to get a robust product rather than a fragile one.
- Internal standards mandate bulletproofing, at least against Oopses that will get your ass sued, even more strongly than the urge to get the product shipped this quarter.
- External standards like the software Underwriters' Lab under discussion become well enough known that Joe Consumer demands the seal of approval even if he doesn't know what it involves.
But if bulletproofing isn't in the spec it's unlikely to happen. And as a side note, the acceptance test is the spec.
