- fork this repository
- write all of your code in a branch named
lab-#
; +<your name>
e.g.lab10-amanda
- push to your repository
- submit a pull request to this repository
- submit a link to your PR in canvas
-
Study and research the Towers of Hanoi. Programatically solve this problem by creating a method that brings in (n) number of disks, and outputs the final number of moves.
-
Try and use recurison
- Do it iteratively
A README is a module consumer's first -- and maybe only -- look into your creation. The consumer wants a module to fulfill their need, so you must explain exactly what need your module fills, and how effectively it does so.
Your job is to
- tell them what it is (with context)
- show them what it looks like in action
- show them how they use it
- tell them any other relevant details
This is your job. It's up to the module creator to prove that their work is a shining gem in the sea of slipshod modules. Since so many developers' eyes will find their way to your README before anything else, quality here is your public-facing measure of your work.
Refer to the sample-README in the class repo for an example.
-
7pts: Program meets all requirements described in Lab directions
-
3pts: Code meets industry standards
-
Readme.md required for submission. Missing readme document will result in a best score of 2/10