Student "edition" found at {csi dot journalspace dot com}.

Maybe I shouldn't have started this blog now, not with everything that's been going on.

I have one class right now that is at the cusp of a change between flowcharts.

In the previous batches, computer systems organization did not have switching theory as their prerequisite, until one of their teachers complained.

So for this batch taking computer systems organization right now, they took up the first part of the digital design book already.

But there remain at least three students from the previous batch who have not taken up switching theory; it's not in their flowchart.

But computer systems organization is. So I have five students who've taken up the basics, two who are encountering it for the first time, and one who was in my previous class but disappeared during the last two exams, so he's repeating the subject.

One of the two I've mentioned now wants to drop the subject because he did not take up switching theory, feeling he has to take it first.

The associate dean wants me to discourage him from doing that, since it's not a valid reason as it means the teacher is not doing something right.

When I talked to the student and told him he will be delayed, I got the rationale back that he's already delayed anyway.

So I had to frighten him with saying that not all of those who took up switching theory passed. And that I'm already adjusting especially for them, so that if he takes computer systems organization under another teacher, he might not get the same consideration.

It's good to see that he wants to learn, and that he's frustrated with what he doesn't know right now that his classmates do, but I would like to be the one to mold that enthusiasm that has to be by not accepting his presumption of defeat.

Session 2367 almost promised doing everything to make sure they pass. Class dismissed.