Lab 4: Project 1A Peer Code Review


In this lab, you will compare your solution to project 1A with 1-3 other students in your lab. On-time attendance is required this week. If you cannot attend your regular lab, you may attend another instead. If (and only if) you are unable to attend any lab at all, please fill out this exemption form.

LinkedListDeque Overview

Your TA will start the lab by giving a brief overview of the staff solution to LinkedListDeque.

LinkedListDeque Peer Review

Group up with 1-3 other students and compare solutions. Programmers in 61B vary widely in their level of experience and comfort with programming. Our goal here is to help each other get better. Please be nice, and don’t feel bad if your solution is less elegant or even downright ugly. I’ve certainly written incredibly ugly, inelegant code! Why here’s a 1600 line monstrosity I wrote in 1997, and a video demo of it running if you’re curious what it does. knaveos will not be on the midterm.

Avoid the temptation to explain exactly how your implementation works to your partner. Instead focus your discussion on more specific questions. Some suggested questions are listed below:

  1. What was the most annoying bug you had and how did you fix it? Did you use the debugger? Did you fix it by adding special cases? Did you do any change-and-pray (where you make a tiny change and hope the AG approves)?
  2. Did you end up cutting anything out to make your code simpler? If so, what?
  3. Do you have any special cases in your code?
  4. Do you have any private helper methods?
  5. Does your code repeat itself anywhere? Would private helper methods have helped?
  6. Were you able to call or reuse code anywhere (for example, in the copy constructor)?

After discussion, fill out the first half of self_reflection.txt with your own self reflection.

ArrayDeque Overview

Your TA will go over the ArrayDeque solution.

ArrayDeque Peer Review

Now, pair up again and discuss your ArrayDeque solutions as you did for LnkedListDeque. Fill out your self_reflection.txt. We recommend that you talk to different people than you did for ArrayDeque, but it’s OK to stick with your group for ArrayDeque.

Self Reflection and Submission

Make sure you’ve filled out out at least 4 of the questions in the self_reflection.txt document provided in the skeleton. Ask a TA to check your self_reflection.txt and give you the magic word to put in magic_word.txt. Push to Github and submit to Gradescope.