It's funny how a random soundtrack choice by your music player can make you realize how much you've changed over time.
So, a few of the teachers - in fact, all the teachers I have but one - have sent out emails saying that, apparently, most of the class is failing, and so they'll go more slowly, and that this really isn't hard and that we should try harder.
Quick diversion here.
One problem a lot of people have with interface development is that people do the wrong thing. Consistently. The coder sits there, staring in disbelief, as one person after another makes apparently stupid decisions in what to click on. "But it's obvious!" the coder cries. "These people just suck!"
Eventually, they have a revelation. They realize that people *do* suck, yes, and it's the interface designer's job to make the interface work anyway. If people can't use the interface, it doesn't matter how much you say "but it's a good interface!" - the fact is, it's a lousy interface.
Let's go back to the teaching.
If people aren't learning, it doesn't matter how much you claim it's the students' fault. Chances are, it's just a bad teacher.
So, what does it say when the majority of students, in the majority of my classes, are failing? Myself possibly included, judging by the number of times the teacher has totally forgotten major things we had to turn in until it's too late? (Yes, the TEACHER, unless 95% of the class missed the same thing.)
Yeah. I gotta get out of this school.
I'm sitting in the SUNY computing lab right now, and I'm about to go print something. There's a twenty-person-long line, but that's OK.
As usual, nobody's using the Mac.
Time to go skip the line!
Followup: I skip the line, use the Mac, print out what I need, and leave. I pass the line, turn, and look for a minute.
Nobody's moving to use the Mac.
I say, "Guys, you realize the Mac prints just fine?"
They look at me in confusion.
I give up.