Open Source Software
There are some heuristics how to evaluate Open Source Software.
- written to solve author's real-world problem.
- has a distinct visionary, architect, leader.
- built using bottom-up process.
- modeled as a stack of separated layers.
- acts in an appropriate abstraction level.
- uses specialized services provided by OS.
- reuses only high-quality third-party components.
and a list of bad symptoms:
- fail to understand abstraction layers.
- attempts to manage an underlying OS from within JVM
- believe that JVM is the best target platform.
- believe than NodeJS could be fast and efficient.
- believe that NodeJS could solve a concurrency problems.
- believe that MongoDB is reliable storage.
- believe that Cassandra is reliable or efficient.
Note: See TracWiki for help on using the wiki.