Read through the comments in the code. The solution can be done in a single function.
- If you are new to Git, review this.
- Do your work on the
solutionbranch. - Commit and push to the
solutionbranch as much as you want -- as much as needed. - To submit your assignment will be to create a PR (Pull Request) in your repo from
solutiontomaster. This will signal us that your assignment is ready for review. - Use the slack channel if you have any issues or questions -- definitely seek help if you don't understand Git or the PR process for submission.
- Complete the add_contact(contact) function (line 47).
- The included contacts and print statements should work.
- Extra credit, create a separate unittest file to test your function.
- Also, you should be able to explain what is happening, why it is important and what technologies actually use this approach.
| Criteria | Superior (5) | Excellent (4) | OK (3) | Not OK (2) | Unsatisfactory (1) | Grade/Comments |
|---|---|---|---|---|---|---|
| Readability (50%) | The code is organized (modular) well documented, easy to read and follow. | The code is easy to read and well documented. | The code can be followed. | The code is not easily followed. | The code is a mess. | |
| Specifications (40%) | The program works and meets all the requirements. | The program works and meets most of the requirements. | The program produces correct results but does not display/plot them correctly. | The program does not meet most of the requirements or fails to display or plot any. | Program does not work at all. | |
| Efficiency (10%) | The code is highly efficient without affecting readability. | The code is reasonably efficient without affecting readability. | The code runs within a few seconds. | The code runs within a few minutes. | The code takes over an hour to run (or doesn't run at all). |