People think that computer science is the art of geniuses but the actual reality is the opposite, just many people doing things that build on each other, like a wall of mini stones.
— Donald Knuth
This week A1 will take place, you can continue working on your prototype.
In the lab we'll do a peer review by having a look at the assessment checklist and grading fellow students based on the rubric. After that teachers have time to answer questions.
A1 review:
This is a peer review document you can fill-in on the project of your fellow student. It's a good last check to see if everything is in order.
→ Review
A1 rubric:
This is the rubric your teacher will grade you on. Give your fellow student a grade based on the rubric. Ask yourself upon completion if everything is clear and that you understand each row and column, if not ask your teacher!
→ Rubric
Questions:
Make sure you come to the lab prepared in advance:
- Know which questions you want to ask.
- If you have a bug, investigate and try to make a detailed explanation of your problem.
- Ask other students if they encountered the same problem.
Read more about asking questions
Based on your repository, source code and live version you show what feature you've created for back-end. The idea is not to present your feature, a teacher will look through the code and ask questions. By answering questions you demonstrate sufficient knowledge of our goals. This is an individual test, so they will be conducted between one teacher and one student.
→ Read more about assessment 1
→ Go to the scheduler on Brightspace
- Bring your own computer and a charger
- Have the latest version of your code ready in your editor
- Open up your docs inside of your GitHub repository
- Have a live version up and running
Make sure you hand-in your work in the assignment on Brightspace
- A link to your repository
- A link to your live project
- A
zipfile of your code (for archive purposes)