Comment Sleeping in lectures (Score 1) 297
Following the urban/almost true stories here..
There's this professor in an introductory class of computer science at our university. Now, these classes are filled with fresh young people, eager to learn about computers, and as I started studying in 98, at a time when job prospects were promising. Thus, lots of people had chosen computer science.
Now, you might think that this ended up with classes full of people with no clue what so ever to computing. Well, you are right. The problem with this professor though, was not that he went through the stuff too fast or too slow, but that he didn't went through his stuff.
The professor, well known for his mac addiction, spent most of lectures showing of his macintosh and talking about how stupid and non-useful those old mainframes used to be.
There are some highlights in all his stories, as when he talked about programming classes in the old days at high school. The students started on Monday, writing their programming lessons on paper. On Tuesday, the code was reviewed and typed into punchcards. On Wednesday, the cards were sent to the university, layed on batch for compiling. On Thursday, the compiled programs were runned, and on Friday the results returned to the high school. They now had the whole afternoon to debug so that they could rewrite whatever neccessary on Monday to make it work.
Now, focus, stain, focus. Back to the story. I forgot to say something about Extreme programming and nowadays and checkin-each-minute-cycles.
The thing was, on one lecture, the professor started up with his slides, gradually shifting to some example he had found in 1987 that he just needed to show everyone. This example, of course for the Macintosh, required the lowest possible resolution and color depth, and the professor fickled and tried to locate the Screen resolution dialog (hurray for usability, Apple!). Nobody cared. Students small-chatted about were to go drinking in the upcoming weekend. (Samfundet!)
Suddenly a student started snoring, but nobody could figured out who. Everyone laughed, even the professor. He's a good hearted guy, but he made a point of the abuse of time to come to lectures just to sleep (08:15 lectures aren't called 'night shift' without reason). The lecturer continued, "I suggest for the sleeping person to leave now, get some sleep at home, and rather spend the afternoon playing with the lecture examples. " Then, fifteen students raised and leaved the room. More laughter.
There's this professor in an introductory class of computer science at our university. Now, these classes are filled with fresh young people, eager to learn about computers, and as I started studying in 98, at a time when job prospects were promising. Thus, lots of people had chosen computer science.
Now, you might think that this ended up with classes full of people with no clue what so ever to computing. Well, you are right. The problem with this professor though, was not that he went through the stuff too fast or too slow, but that he didn't went through his stuff.
The professor, well known for his mac addiction, spent most of lectures showing of his macintosh and talking about how stupid and non-useful those old mainframes used to be.
There are some highlights in all his stories, as when he talked about programming classes in the old days at high school. The students started on Monday, writing their programming lessons on paper. On Tuesday, the code was reviewed and typed into punchcards. On Wednesday, the cards were sent to the university, layed on batch for compiling. On Thursday, the compiled programs were runned, and on Friday the results returned to the high school. They now had the whole afternoon to debug so that they could rewrite whatever neccessary on Monday to make it work.
Now, focus, stain, focus. Back to the story. I forgot to say something about Extreme programming and nowadays and checkin-each-minute-cycles.
The thing was, on one lecture, the professor started up with his slides, gradually shifting to some example he had found in 1987 that he just needed to show everyone. This example, of course for the Macintosh, required the lowest possible resolution and color depth, and the professor fickled and tried to locate the Screen resolution dialog (hurray for usability, Apple!). Nobody cared. Students small-chatted about were to go drinking in the upcoming weekend. (Samfundet!)
Suddenly a student started snoring, but nobody could figured out who. Everyone laughed, even the professor. He's a good hearted guy, but he made a point of the abuse of time to come to lectures just to sleep (08:15 lectures aren't called 'night shift' without reason). The lecturer continued, "I suggest for the sleeping person to leave now, get some sleep at home, and rather spend the afternoon playing with the lecture examples. " Then, fifteen students raised and leaved the room. More laughter.
(ok ok, I did combine some stories to make this one, but it is true! It's true!!! heheheh )
Btw, I had to use Plain old text for this posting to allow HTML, not Extrans (html tags to text). That's usability!
