-
Notifications
You must be signed in to change notification settings - Fork 0
Sermons from the Rock
First Commandment:
Thou shalt instantiate Classes
Interface Commands, et al
Landmark
User Admin should be a User with special role Define roles
Game It's okay to install a timer program from elsewhere, we'll probably have to apt-get it. See also the Third Commandment
Storage class with dictionary in it (i.e. username/password) Eventually this should have methods to pull data from a text or csv file or whatever, but for testing/design purposes we can probably just push through dummy data
Second Commandment
Thou shalt utilize the methods of agile development
For example, we DO need to use test-driven development, as otherwise we get no points. There will be a rubric provided on 10/26 in class that should clarify this.
We need to start making tests for each method as we did in class. Using the framework we have (once finalized) we describe the behavior of the class via tests (i.e. "if input a, should output b")
Also, we should post all meeting minutes and such to D2L discussion board so the Rock and his dread Apprentice Tanawat can follow along.
Third Commandment
Thou shalt not treat this too much as a real product or fall victim to creep of thy scope
As long as it works as advertised on our own machine, we don't need to worry about anything else. We won't be hooking it up to an SQL or oracle database, we'll be using text files for i/o (eventually). This also means we don't need to worry about packaging it for distribution or copyright or any of that - for example, the timer code that we'll likely use has to be added to the user's local Python install, and that is fine.
Fourth Commandment
Thou shalt obey the testing goat.