Class 31 — November 3
We know you can
You are ready now – For problem solving prowess – Your best will be shown
Look both aways
Remember
- The University accepted you because you are an outstanding student.
Agenda
- Document your accomplishments
Please
- To make things go smoother, you are strongly encouraged to submit as you go along
Resources during test
- Built-in functions
Downloads
- There are three modules and three testers to download
Take note
- More exhaustive testers will be used during grading. Passing the provided simple testing does not guarantee your solutions are perfect.
Important
- I suggest you do things the easiest way possible.
- Always think before coding.
- Always think how you would do it if you had to do it by hand.
- There are no intended trick questions – each module has a straight-forward answer
- Whether a module compiles (i.e., no syntax errors) so that it can be tested is important.
- If you cannot get a function to work, still submit it along with comments on how you would do it. Make sure every function has at least one non-commented out statement (e.g., pass ) or it will compile with errors
- Make sure there is no debugging and print code in your functions when you submit. Make sure modules only have the function definition in them. Do not include program code after the function definitions.
- Do not leave the room without checking that all of your submissions have been correctly uploaded. A forgotten submission will get a 0.
- Uploading after you leave the room means you want to withdraw from the class.
- Modules should demonstrate proper programming style; e.g., whitespace, identifier naming, etc.
