Ignore for the moment the fact that this article is about open source code, and pretend it's about open educational resources or something similar. The advice it give becomes spot-on. For example, is it readable? "Readability can be good naming conventions for identifiers, good spacing, clear readable logic, well-understood scopes." Exactly. Is the resource actively maintained? Is it well-tested? Are other people using it? And is it documented? "Documentation makes [resources] much easier to understand, use and modify. It’s also a great indication for the thought and carefulness the developer who wrote the [resource] put into it."
Today: 1 Total: 25 [Direct link] [Share]
