Spring 23-24
------------
- debugging/testing section was good to include, but a bit preachy; maybe frame more about why we are covering it specifically in 107; debugging 107 C programs is hard, techniques will save time
- quiz a bit of a duplicate of lecture practice, maybe a bit too easy

Spring 24-25
------------
- first bullet above still sort of applies, but not a huge issue
- just got through everything, a little rushed at the end but started a few minutes late.  Slides have a lot to get through
- fix table, updated wording in char * vs char[] table at end isn't at start
- lots of complexity about char[] vs. char *, but does it matter as much as the complexity it entails?  wonder about ways to skip over more of the nitty gritty details if we don't need to worry about them
- poll question was good, add diagram to slides?  even if I still whiteboard it
- quiz question updates - add testing question about tests before writing code, incremental testing to deduce that bug is from recent change, and also about read-only strings (from spr24 lecture quiz).  Need to spend more time talking about testing slide to cover info for these questions.
- room to cover const (instead of assign2 spec?)
- don't cover dereferencing, but referred to in lab2
- double check lecture description in calendar and learning goals

Spring 25-26
-------------
- quiz question updates; want to cover incremental testing (need to mention in slides and verbally), read-only strings
- trim Valgrind demo slightly
- worksheet was great, people had questions, want time to circle, e.g. about how buf2 + 2 worked since it was an array
- room to cover const?
- dereferencing, ptr[0] and *ptr
- double check lecture description in calendar
- update string rules slides, trim down and focus on most important
- trim debugging guide walkthrough
- debugging check-in poll question (see lect 11)