Lesson Outline
| 50 min | GP4 Review
* Example review form Instructor Demo ~5 min 09:43 – Team 4 parking 09:49 – Team 5 spotifind 09:55 – Team 6 seal 10:01 – Team 7 runtime 10:07 – Team 1 programu 10:13 – Team 2 mydex 10:19 – Team 3 foodies Peer Review ~10 min 09:43 – Team 6 reviews Team 3 09:49 – Team 7 reviews Team 4 09:55 – Team 1 reviews Team 5 10:01 – Team 2 reviews Team 6 10:07 – Team 3 reviews Team 7 10:13 – Team 4 reviews Team 1 10:19 – Team 5 reviews Team 2 |
|---|---|
| 15 min | Debugging
* Server side: Debugging in Visual Studio Code * Client side: Debug JavaScript - Chrome DevTools |
| 10 min | Team Reflection
* See details below |
Before Tuesday
Project: Minor revisions before grading.
Homework: Start on HW6 (due 4/10).
Team Reflection
You've been working on this project for a while now and have made dozens of changes to your code. In fact, some teams have made over 100 commits in their GitHub repository! Now that you've built up some history, you can use Gource to see your project evolve over time. From the command line, simply run gource in your git project directory. Here are some recommended settings:
gource --auto-skip-seconds 1 --file-idle-time 0 --seconds-per-day 5
As with other programs, you can read the manual (type man gource or gource --help) for more options. In particular, you can interact with the visualization as it runs:
Pressing SPACE at any time will pause/resume. While paused, you can use the mouse to inspect the detail of individual files.
The TAB key cycles through selecting the currently visible users.
The camera mode (either tracking activity or showing the entire code tree) can be toggled using the middle mouse button.
You can drag the left mouse button to manually control the camera. The right mouse button rotates the view.
Take some time to reflect and celebrate what your team has accomplished so far this semester!
See also https://github.com/cs374/.../graphs/contributors (replace "..." with your team name).