Lab 9
Purpose
Practice with list abstractions
Check your past submission
Make sure last weeks lab, if it was submitted jointly, has both partners on it. If it doesn’t, get your partner (who should be in the room) to add you!
Find a partner
Find a new partner in the class. This should not be who you worked with in any previous week. Working effectively with people you don’t already know (and perhaps would not be friends with!) is an important skill to develop.
Starter File
Download lab9.rkt. Start working through this, carrying out pair programming like the TAs demonstrated. Be sure, every time you see the phrase “Design the function”, to follow all the steps of the Function Design Recipe. Stop when you get to the place where it says “STOP AND SWITCH WHO IS TYPING”.
Stop and Switch Who is Typing
An important part of pair programming is that the same person isn’t always typing. At this point, whoever was using the computer should switch. You should also, at this point, submit what you have done so far to the Lab 9 assignment on Gradescope, and add your partner to the submission.
Also – indicate to the lab TAs that you are now ready for Code Review, which will take place on Part A.
Code Review
At some point before the end of lab, you should have a TA come over and review Part A. You can pull the work up on Gradescope, which both you and your partner should have access to.
You should be able to explain, in no more than a minute or two, how your code works and why you made the choices you made. You and your partner will be explaining to separate TAs at the same time, so make sure you know, yourself, what you did and why: your partner will not be able to help you explain.
Continue with the Lab
Concurrent with the code review (which will proceed throughout the rest of the lab), work on Parts B, C, D & E.
Finished?
When you have completed all the exercises, you should resubmit the completed file to the Lab 9 assignment on Gradescope. You only need to submit one copy as a pair: have the submitter add the other partner to the group after submission. If you have trouble submitting it, ask a TA. Ensure that the autograder, which runs immediately, correctly validated your work, and if there are problems, correct them and re-submit. Note that Part D will be manually graded later!
Once you have submitted the problems, and have completed your code review, you are welcome to leave!