andrewducker: (Default)
andrewducker ([personal profile] andrewducker) wrote2012-02-23 11:00 am

[identity profile] steer.livejournal.com 2012-02-23 04:53 pm (UTC)(link)
In my case when I do the lecture I'm also taking questions from students, explaining parts where they do get stuck, asking them if they understand where we are at so far... posing questions for thinking about in the break and giving demos of software.

Students have an opportunity to privately discuss with me at the end as well.

However, for the top-end students, missing the lecture and reading the notes might well be 90% as good. That said, I've regularly encountered high-flying students who miss out on learning because they are good enough to get through without reading lecture notes and sometimes have missing techniques in their armoury -- so I've occasionally taught students who were better coders than I am and sometimes regretted that they felt there was little they could learn by going at the pace of the majority.

I'm perfectly happy for students to skip the lecture and read the notes but unfortunately my institution is not and attendance is compulsory and checked with a register -- I wish it weren't.

[identity profile] khbrown.livejournal.com 2012-02-25 02:28 am (UTC)(link)
Did the students who were better coders also have a better idea of the underlying theory and algorithms?

[identity profile] steer.livejournal.com 2012-02-27 04:47 pm (UTC)(link)
In my experience there was not a strong correlation between underlying theoretical mathematical ability and coding. I was teaching mathematics undergraduates and post graduates so almost everyone had reasonable maths skills. However, it was often the case that outstanding coders were poor mathematicians and poor mathematicians were outstanding coders.

In general I think a good coder only needs to know "this is the efficient algorithm" to code it not really to understand fully how the proof of the order of execution time follows.

[identity profile] steer.livejournal.com 2012-02-27 04:53 pm (UTC)(link)
Hmm... I think the "chunking" ability is critical -- being able to split a task down into logical sub units -- but it's hard to know if other people go about coding in the same way I do.