Can you explain how being completely intolerant of the fact that students have lives helps with your resource constraints? People will be a couple minutes late. Things happen. I don't think it's reasonable to threaten kicking someone out of the class and failing them for being late once.

Again, if you want to say that you need to make the class as terrible as possible so that people drop, then just say so.

anon, sorry I was not completely clear:

I hate to make this request, but I need half to 2/3rds of the students to drop the course. I'm hoping that you will still be able to learn a lot from the class -- but I need to find a mechanism to make the class smaller. Being strict on attendance seemed like the "least bad" of several rather unattractive alternatives.

I'm hoping that someone has a better idea, and I'm completely open. Please come and see me in 739 Soda.

Far far better idea: cancel all existing registrations and reopen it at 10am next Wednesday. If the system doesn't support that, then say you will be "reregistering" people by hand and the first x to be at your office at 10am Wednesday are in. Doesn't fuck over an entire semester for people. Was really easy to come up with. If you really wanted good ideas you could have asked the class in the first session or on your blog and surely someone would have had a better idea than your horrific plan to make everyone hate you and the class.

Jacalata -- I did look into dis-enrolling students, and was told it was a non-starter.

And I have to say that it is already a huge problem at Berkeley to simply get enrolled into a CS class. There are simply not enough resources to go around. That's why this class has a huge waitlist.

By the way, this problem is also occurring in other classes, but they are scheduled as Monday-Wednesday classes. My class is Tuesday-Thursday -- the first day of classes at Berkeley was 8/29. Monday is Labor Day holiday at Berkeley, so those other classes will have to deal with their situations on 9/4. (However, their TA deficits are not quite as large as those that we have in CS 161).

What prevents TA's from teaching more than 1 or 2 discussion sections? If each of them taught 2~3 discussions, wouldn't everyone be happier? As students, it would be nice to know how the TA hours are managed. TA's earn a lot of money for teaching. Does a 20-hr TA do 2 hours of discussion, 1 hour of office hour, 1 hour of discussion prep, 1 hour of making homework, etc? How does it add up to 20 hours? Do they have to redesign the entire class and grade homework problems? If necessary, can they take one more hour of discussion from one of the other responsibilities? It would be great if the teaching staff is clearer and more open about this.

Another_anon -- that's a great question, but I cannot answer personnel questions in a public forum -- if you want to drop by 739 Soda, I'll be happy to try to answer your question.

Our course has what Berkeley EECS calls "30 hours of TAs." I can assure you that they'll end up doing a lot more than 30 hours worth of work each week.

I'll also remind you that our teaching assistants are unionized, and we are bound by contract rules.

But even if I had the power to change that (and I do not), you can see that it would have to change for every single EECS class -- why would a TA want to teach 4 discussion sections for CS 161 when s/he could get the same pay credit teaching 2 discussions sections for another CS class?

I don't know how much I can say, but 1 section of any class is 10 hours of TA paid time. Period. Doesn't matter if you work less or more.

Though, often times, most TA's I know put in far more than their required time.