Once again, I'll try not to talk much today (after the preliminaries).
Review session tomorrow at 11 am. (Should I stop offering these?)
Reflections on Epilogues
Notes from Epilogues on HW 3
Not all of you filled in the epilogues. Please take the time to do so.
Evidence suggests that you learn better if you bookend your assignments:
Think about the work in advance, do the work, reflect on it.
This approach can also help with more general skills, such as
reading tasks and assessing workload.
Each person should fill out his/her/zir own epilogue. The goal is to
reflect personally, not as a group.
Some interesting responses
"We did not predict all of the complexities."
Are there ways you might improve your skills in identifying
Do it by hand.
"Debugging was hard!"
We're working with the debugger today, which may help.
Evidence suggests that if you think more carefully about the
problem before implementing, you'll have less debugging.
Generally budget the same amount of time for debugging as you
spend on design and implementation.
"I did not read the assignment closely enough."
Time spent: 5-10 hours
How do we make you more efficient while helping you learn,
particularly since the best learning often happens when you
Friends of Drake Library needs help setting up for their annual booksale
on Thursday, October 2 (conveniently, the same night as Grinnell High
School's homecoming parade). You can help a good cause and probably get
a few free books, too.
Quick Comments on Debuggers
We all learn to debug with print.
Print statements clutter your code.
We can do better!
And good debuggers are better at helping you find errors
(e.g., you can run a program until a certain state is reached)