Code Review is the time to catch issues and provide intervention for students who don't understand the concepts from the week. The length of Code Review will vary from group to group, and may take between 90-120 minutes. With sufficiently advanced students, push them like they would be pushed in a Technical Interview. Follow this outline for a successful group code review.
Ideally, Code Review will take place in groups around a TV or projector screen. You will guide the discussion as each student presents code from their project.
Review the following points with each student in the group:
- All projects are pushed to Github with detailed commit messages.
- Each project is complete and functioning.
- There are no exceptions or warnings.
- Classes, properties, and methods follow proper naming conventions and style.
- Code is written by the student, not copied and pasted from solution branches.
- Work with the student to determine a rating (1-3) on each objective from the week. Ask specific questions for each objective to determine understanding. Ask to see examples of each objective in the projects as evidence of understanding.
Rating Scale:
1 - Does not understand
2 - Understands with assistance (mentor, documentation, sample code)
3 - Understands independently
-
If the student is rated at 2 or lower, work with him or her on the objective. Invite other students in the group to give feedback. Provide extra practice so they can get to a 3 in future code reviews. As needed, reteach and provide resources or practice on poor objectives.
-
Report the scores for each objective using the iOS Student Success Tracker. If you do not have access, contact your Lead Instructor.
Discuss the Capstone Progress. In early weeks of class, discuss ideas, frameworks, and user tests to help the student firmly decide on a project. Once projects have begun, do the following:
- Review the App Canvas
- Discuss progress and update the tracker
- Identify the biggest challenges blocking progress
- Pair program on the big challenge
- Give a specific challenge to the student to keep making progress
- Set goals for the student. Focus on student deficiencies first, then black diamond or advanced work.
- If working on team or capstone projects, review architecture, design, and progress on the project.
- Give them specific work to do before the next Code Review.
Update scores in the Tracker. Please consider the following in your scores:
- Attendance in class
- Communication with you
- Ability working with frameworks taught prior to this week
- Ability working with frameworks taught this week
Include any feedback or notes that will guide intervention (help) for the student.
If there are any specific needs or concerns with the student, contact your lead instructor.