Cracking method and command line interface successfully implemented
Project is broken into logical components consisting of at least 4 classes that have single responsibilities. No more than 2 methods are longer than 7 lines. No class is longer than 100 lines. While there may be 1 or 2 lapses, variable and method names clearly communicate purpose.
All test names clearly communicate the purpose of the test. At least one test implements mocks and stubs. Test coverage metrics show 100% coverage
At least 40 commits. At least 15 pull requests that are named and documented to clearly communicate the purpose of the pull request. No commits include multiple pieces of functionality. No commit message is ambiguous.