Re:80-20 software
by rwmj on Monday July 23, 2012 @04:04AM
(#4280038)
One way to mitigate this is to reduce the cost of maintaining those little-used features.
I've been doing this by (a) having a huge automated test suite that covers just about every feature (you don't get a feature in unless it has a test), and (b) being very aggressive about generating code, and (c) using Coverity to automatically find bugs.
The automated tests (a) let us know if a little-used feature breaks because of an unrelated change. That lets us decide whether to remove or fix the feature without the feature being a constant burden. Generating code (b) lets us make global changes to boilerplate without micro-managing each feature. And using code quality tools (c) is self-evidently better when you have a large codebase.
I've been doing this by (a) having a huge automated test suite that covers just about every feature (you don't get a feature in unless it has a test), and (b) being very aggressive about generating code, and (c) using Coverity to automatically find bugs.
The automated tests (a) let us know if a little-used feature breaks because of an unrelated change. That lets us decide whether to remove or fix the feature without the feature being a constant burden. Generating code (b) lets us make global changes to boilerplate without micro-managing each feature. And using code quality tools (c) is self-evidently better when you have a large codebase.