|
|
|
|
|
by paxys
1059 days ago
|
|
In my experience it's always the former. Back in university the surest sign of a good class was that you were allowed to "cheat". The professor encouraged using any and all outside materials for your assignments. You were allowed to work with other students on projects. Exams were all open book. You could use open source code. Such classes always led to the best outcomes for students who were truly interested and engaged, and those who weren't had no way of faking it. On the other hand classes where professors spent more effort on detecting cheating than teaching the material were always duds. |
|
Some students ignored his rants because they didn't find the subject interesting, did the past papers, and then got to the exam and did terribly, then complained about the fact that "it's all based on his rants".
Others found the ranting engaging because it was deep dives on obscure bits of computer security history. My year he spent ~4 weeks going on about Stuxnet, including deep dives into the wider political context. When I got to the paper, one of the few questions we could choose, for 50% of the paper, was just "What was Stuxnet". I wrote pages and pages. Figured out from marking that I got full marks on that one. I always did great in that lecturer's modules despite never taking notes and rarely doing any targeted reading.
To show the level of engagement, I once turned up to one of these lectures 10 mins late, with most of the class already there, and the lecturer said "oh I wondered where you guys were, I guess I'll start again". He knew we were the only ones who cared about the class.