Week 5 [Feb 10] - Tutorial

1 Discuss iP progress

Quickly update the tutor about your iP progress:

• Has at least one team member managed to set up Travis?
• Has everyone completed Level-10 (i.e., the GUI) and A-Gradle? Any GUIs that went beyond the JavaFx tutorial?
• Anyone has iP increments overdue more than one week?

2 Discuss the code quality of iP PRs

1. Updated instructions: Review PRs of the other team. You can find the team information from here.

   Team	Discuss PRs of
   Team 1	Team 2
   Team 2	Team 1
   Team 3	Team 4
   Team 4	Team 3

2. Locate PRs from that team: Go to the list of Duke PRs. Locate the PRs (you can filter using tutorial.* and team.* labels).

3. Pick a PR to review, giving priority to PRs with fewer comments.

4. Discuss abstraction aspect of the code: Go through the code, and discuss the abstraction (SLAP, arrow-head style code, too-long methods, too-deep nesting) aspect of the PR
   To identify long methods or deep nesting, zoom out and scroll through the entire PR code to do a visual inspection (no need to read the code line-by-line). After visually locating a method that looks too long/deep, have a closer look to see it can be improved by using better abstraction.If you are unsure about a case, you can also rope the tutor in to the discussion.

5. Add comments: If the team agrees that the abstraction aspect of specific piece of code should be improved some way, add a comment (team members can take turns on adding comments).
   e.g., This method looks rather long; perhaps it can be shortened using SLAP?

6. Repeat for remaining PRs: Continue to review PRs until the 20 minutes mark.

3 Prioritize tP user stories

• Show your list of tP user stories to the tutor (for progress tracking).
• If you haven't done so already, prioritize tP user stories as explained in the   Project .