Usage

• The README contained everything I needed to easily use the program:

• The program compiles/runs without errors:

  only the main program file should be marked as executable.

• The program worked as advertised:

Style

• The code is cleaning divided into modules and multiple files:

  The main loop could be cleaned up by creating and using a command-interpreter module and creating a 'player' class that could be used to represent both Theseus and the minotaur. This would also open up the possibility of adding multiple advisaries for higher difficulty.

• Variable and function names are meaningful:

• Comments are used where appropriate:

  more consistent use of docstrings

Philosophy

• The program most closely follows the rouge-like interface pattern:

• This choice of pattern is a good one for this application:

• This program follows the Rule of Silence and Least Surprise:

• This program follows the Rules of Modularity and Composition:

  generally a good separation between UI and data, but improvements in separation between control and UI could allow for future expansion to network and multi-player implementations.

• This program follows the Rules of Representation and Simplicity: