(define <name> <expression>)
.(lambda (<parameters>) <expression>)
.(define <name> (lambda (<parameters>) <expression>))
For today’s exercises, we will continue to try out pair programming. Pair programming is a particular discipline of collaborative programming that we will be using extensively in our lab work. We’ll have more to say in the coming weeks about the nitty-gritty of working in pairs, but we would like you to dive head-first into the experience.
Between each exercise, you will swap driver and navigator roles so that you and your partner get experience with both roles. If you are in a group of three, you will have two navigators and one driver! Make sure to rotate roles so that everyone gets a turn as the driver.
To encourage appropriate swapping, we have labeled each problem as “A” and “B” for pairs. Whoever is closer to the board is partner “A” Whoever is further from the board is partner “B”. Partner A or Partner B drives as indicated in the lab. If there is a third partner, ignore the labels and rotate appropriately.
You should begin by copying and opening the file procedures.rkt (click on it) which contains both instructions and spaces for your answers.
As in the previous lab (and future labs), you will work with a randomly assigned partner using a starter file.
All of the instructions are in the file. Switch to that now.
Here’s the “Party Person” picture referenced in one of the exercises.
.
The checkerboard example comes from a very old version of CSC 151. We are no longer sure which member or members of the department wrote it.
Bits and parts of this lab come from procedure labs from other versions of CSC 151.