Features and Scope in Open Courseware
A couple of weeks ago, Brian Granger (one of the core developers of IPython) posted some thoughts on features and scope in open source software. In it, he enumerates some of the risks associated with constantly adding new features to a piece of software (open source or otherwise):
- Additional complexity in the code base (which makes future work more difficult).
- Increased "surface area" for bugs (the more features there are, the more places a bug might be lurking).
- Increased documentation and support time.
- It forces developers to specialize, which makes "big picture" thinking harder.
- Increased testing effort.
- A more complex user experience. (Microsoft Word, anyone?)
- Opportunity costs: time spent working on X is time not spent working on Y.
He then enumerates some things projects can do to throttle growth down to manageable levels:
- Explicitly list things that are not going to be implemented, i.e., define a limited scope for the project.
- Make features fight hard to be accepted and implemented by telling the community that the default answer is "no".
- Separate feature requests from other issues.
- Discuss costs and liabilities as well as benefits whenever a new feature is proposed.
- Be willing to remove things.
He also lists some questions projects can ask:
- What fraction of your user base will use the feature, and how often?
- Can it be added as a plugin?
- How difficult will it be to test, debug, document, and maintain the feature, and what fraction of your development team is capable or interested in doing this work?
- Can you implement the functionality in a more limited, but much simpler manner?
Everything Brian says applies directly to open courseware like Software Carpentry. People constantly suggest new topics that could be added to our material, but few of them say, "...and I'll write it," and more often than not, the topics are things that would interest only a fraction of scientists. We have therefore been cutting back on material rather than expanding it: as useful as Make, object-oriented programming, image manipulation, and disciplined use of spreadsheets are, they just aren't useful enough to justify expenditure of our scarcest resource—time.