Code Walks
Many companies ask employees to conduct "code walks" before code is committed to the code base. During a code walk a pair of programmers presents the code to a panel of reviewers. The goal is to find flaws in design, errors, algorithmic (performance) problems, and other bugs before the product gets released. Several downstream courses offer code walks.
Opportunity
This year, Fundamentals I will offer code walks for the first time. Two highly experienced tutors will conduct code walks on Wednesday evenings and Sunday afternoons.
Signing up is entirely voluntary but a pairIf you work on problem sets alone, CC your head TA when you sign up so s/he can verify your status. must jointly present the code base and will get evaluated jointly. If you do well, you may collect up to three (3) extra points for the quiz category of the final grade per code walk. That is, you can make up for up to three (3) failed quizzes and/or collect up to 13 percent points of your final grade for a category that is worth 10 percent points. You cannot lose points due to a code walk.
Naturally, the presentations will help you improve your communication skills and feedback from these code walks can also help you improve your code base.
Presentations
The two of you will present your current Hungry Henry code to the panel via an overhead projector. The presentation must proceed in follow the "World Design Recipe" (data definitions, main function, rendering functions, event handling functions) and the "Function Design Recipe" for each of the functions.
Your code must be arranged in this way so that the presentation is easy to follow.
Finally it is imperative that your code is clean and that all superfluous junk is removed (un-used data definitions, templates, other disconnected material).
The panel will provide oral feedback and an email with high-level suggestions. You are obliged to address these and let the panel know how you went about it.
Sign up
Spencer Florence (florence at ccs.neu.edu)
Ryan Plessner (rpless at ccs.neu.edu)
subject write "Fundamentals I code walk",
cc your partner (your head TA if you’re working alone), and
body specify either a Wednesday night or a Sunday afternoon slot.
body specify both parterns MyNeu emails
thread reply all to every email
Procedure
If you are selected for a code walk, you will receive email (at least) 24 hours ahead of time. You must bring a laptop with your current code base and any necessary adapters (probably needed for Mac hardware). Failure to do so means you cannot conduct the code walk.
Time and Location
Wednesday: 8–10pm, West Village H 366
Sunday: 2–5pm, West Village H 366
- Wednesday Nov 6th
Start Time
Pair
8:00pm
Logan Wells & Zheng Ru
8:45pm
Julia Wiochowski & Jeremy Stern
9:30pm
Andwer Gilbert
- Sunday Nov 10th
Start Time
Pair
2:00pm
Marc Tawfik & Kiril Voloshin
2:45pm
Kurt Marcinkiewicz and Ryan Lough
3:30pm
Connor Yu and Thomas Levine
4:15pm
Wentao Xiao & Ariana Rosa
- Wednesday Nov 13th
Start Time
Pair
8:00pm
Zeina Migeed & Sherry Son
8:45pm
Anh Tran & Micheal Sestito
9:30pm
Joseph McGurk & Guillermo Saracco
- Sunday Nov 17th
Start Time
Pair
2:00pm
Michael Sestito & Andrew Hombach
2:45pm
Brain Desnoyers & Albert Chung
3:30pm
David Nicholson & Lana Schybria
4:15pm
Lydia Auch & Taylor Vonk
- Wednesday Nov 20th
Start Time
Pair
8:00pm
Xinyan Deng & Derick Brito
8:45pm
Rebecca Chang & Eddie Hurtig
9:30pm
William Silva & Chris Panella
- Sunday Nov 24th
Start Time
Pair
2:00pm
Brett Krutiansky and Jarred Lien
2:45pm
Alexandre Jolly and Kevin Zhou
3:30pm
Matther Kolsosick & John Howard
4:15pm
Jamel Hamani & Hussein Abou Nassif Mourad
Wednesday Nov 27th: SCHOOL CLOSED
Sunday Dec 1st: SCHOOL CLOSED
- Wednesday Dec 4th
Start Time
Pair
8:00pm
Jeffrey Asselin & Lauren Beaton
8:45pm
Matthew Yudysky & Ryan Aljondi
9:30pm
jabos.st & dunn.mat