Here is a reminder of who is doing what for our reference:

• BigInt: Noah, Evan, Alex, Eleanor, Gabriel, Udval, Rockwell, Alessandra, Dylan and Donovan [Period 1B]. Abi, Jack, Blu, Alex, Anupama, Colin, Hisham, Rehoboth and Yuri [Period 4B].
• Card Games: Zach, Luis, Jake (euchre) and Toby (blackjack) [Period 1B].
• Rock, Paper, Scissors: Grant
• Network Connections and Mock Objects: Conrad
• Ncurses Minesweeper in C++: Nikita
• Networked Crazy Eights: Brayden
• Delay Audio Plugin: Gabriel

I'll begin class by reflecting on the work I saw when I evaluated your git repos over the weekend. The grades were not as good as usual: A: 10, B: 2, C: 13, D: 1, E: 5.

I assert that you can only learn to program by programming, so putting in the time is essential if you want to learn to program. The reason for the high number of C grades is that you did not have any commits between class periods. With only two weeks remaining in the semester, you will hopefully fix that practice during these remaining weeks.

Our hardworking, overachieving friend José Ejemplo put in 5 hours working on BigInt this past weekend, and he got the overloaded + operator to work for positive BigInts as well as helping me prepare today's lesson.

I'll take a few minutes to describe how he did it, including taking a look at his commit history. I've mentioned in class several times now the quote Uncle Bob shares in his book Clean Code: A Handbook of Agile Software Craftsmanship by UML creator Grady Booch who said,

Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control.

For those of you who aspire to become highly skilled software engineers, I encourage you to read over the blog post by Brian Norlander, Stop Writing Code Comments.

We'll then talk briefly about any support you need for your projects, and let you get back to work on them!