As I sit here in my last semester implementing a few chosen functions of a small but complete RDBMS for my databases class (i.e. most of the code was written, we just had to fill in stuff relating to a certain topic (buffer management, heap files, etc.)), it makes me wish that I would have seen how the whole system was developed from the first thought processes to the final debugging. That would have been a much better learning experience.
Many who show a mastery in coding are working on the next-big-thing and not furthering their theoretical knowledge.
This is just my thoughts, however. I really have no experience in learning to code in university (2 semesters of intro ECE).
I completely disagree. At least at Northwestern, the systems people know their stuff. You may be right about the theory people, though.
During office hours and personal consultation I would also do live coding with students, but that wasn't rehearsed. In some cases it went really well, in others, it didn't (usually because something would just take too long -- or maybe because it was Scheme). Still, I enjoyed it and I know at least some of the students did.
Maybe this should start becoming a requirement of the instructor?
The great thing about watching them coding "live" is that you can see into their thought processes: which mistakes they make, how they figure out the mistakes and recover from them, exploratory code they write and throw away, the order they do things, how they evolve simple examples into complex programs. You don't get any of that from just seeing the finished product.
It's also great for picking up mundane practical tips, like tab completion, GNU screen, shell history, and how to quickly look up documentation.