Lesson 8: Code Reviews

We have learned a lot of new terms so far! Let's review some of these terms through a game of CS Bingo.

Distribute: Give each student a unique CS Bingo Card.

Do This: Review the instructions for playing CS Bingo.

Do This: Play the music clip to cue the CS Bingo activity. Choose a random definition and read it aloud to the class. Give students a moment to check their bingo card for the correct term, then state the correct term. Repeat until a student yells "Java."

To allow for multiple students to "win" the game, continue pulling definitions until a couple more students win as well.

We have learned a lot about writing code, and our programs are becoming more complex as we learn new concepts. As our programs grow, we must write code that is easy to read and navigate. Software engineers follow guidelines to write their code and use various tools to keep track of their work, access code that they want to reuse in a different program, and request and give feedback.

Do This: Review the lesson objectives.

Group: Place students in pairs.

Do This: Direct students to Level 1 on Code Studio. Students use Levels 1 through 4 to explore good and bad programming styles, comments, how to commit code, how to save classes to the Backpack, and how to import classes from the Backpack with their partners.

Discuss: Click through the animated slide to display the prompts.

• What did you notice in the good and bad programming style examples?
• Why was one programming style better than the other?
• Why would we want to commit code?
• What is the purpose of the Backpack?

Discussion Goal: Students identify aspects of both example programs that made it easy or difficult to read and understand. Students note that the good program example indented blocks of code and included comments to explain the purpose of code segments. Students share that committing code helps create versions of their programs, and the Backpack allows them to store and reuse classes in other programs.

Do This: Click through the animated slide to explain guidelines for good programming style and comments.

Have students share a hobby or interest. Ask students if there are guidelines for doing these hobbies appropriately and why these guidelines exist. Connect with students by sharing an example of your own.

Display: Show the video – Commits and the Backpack.

Software engineers spend a lot of time reading other people's code and providing feedback. Throughout this course, you will use code reviews as a tool for improving your coding and collaboration skills.

Display: Show the video – Software Engineering: Code Reviews.

Distribute: Give each student a copy of the Code Reviews resource.

Do This: Explain examples and guidelines for good feedback.

Discuss: Use the Hold That Thought strategy to discuss the prompt.

• What would be some examples of bad feedback?

Discussion Goal: Students share examples of bad feedback and connect to scenarios where they received bad feedback. Students identify things that make feedback bad, such as not being specific or helpful to resolve a problem.

You can also have students share examples of times when they received bad feedback. Ask students why they considered it bad feedback or what they wish the person giving the feedback had said. Connect with students by sharing an example of your own.

Do This: Introduce TAG for providing feedback.

Do This: Click through the animated slide to introduce the Code Review Call and Response.

The Call and Response strategy helps build community and create routines in the classroom.

You have been placed in code review groups to review each other's code and make revisions to your program based on the feedback you receive.

Do This: Click through the animated slide to have students participate in the Code Review Call and Response.

Do This: Direct students to Level 5 on Code Studio. Students use Level 5 to explore the code review process and practice giving and receiving feedback.

Good programming style and code reviews are an important part of a software engineer's work.

Discuss: Click through the animated slide to display the prompts.

• What surprises you about this visual? What do you want to know more about?
• Approximately $85 billion is lost from developer time spent on bad code each year. How can software engineers minimize this time?

Discussion Goal: Students consider the broader role of a software engineer and the various tasks they complete as part of their work. Students identify strategies to minimize time spent on bad code, such as using good programming style and planning and reviewing code.

Do This: Review the concepts covered in this lesson.

Display: Key Vocabulary

Check For Understanding Question(s) and solutions can be found in each lesson on Code Studio. You can use these questions as an exit ticket.

To assign questions from the AP Classroom Question Bank that align with this lesson, create a custom quiz in AP Classroom by searching the Question Bank for the Essential Knowledge statements listed at the top of this lesson plan. You can find instructions and video demonstrations to do this on AP Central.