3 ms·

Students, take this advice to heart as well. Are all your classes grouped together? They should be. I'd go so far to claim that you should take a less intere

by tsally 17y ago

Students, take this advice to heart as well. Are all your classes grouped together? They should be. I'd go so far to claim that you should take a less interesting set of classes in order to group them all together. I'm taking Distributed Systems this semester instead of Data Mining for this very reason. Am I more interested in Data Mining? Yes. But I'll wait until next semester. Distributed Systems are pretty cool too, and even the most amazing class is not worth adding several hours of dead time to your week. (Interesting note for anyone familiar with Randy Pausch: he mentions this very phemonena in his lecture about time management.)

arjunnarayan 17y ago
Counterpoint: While I agree, I have found that when I have a little spacing between classes per week (say one hour between lectures on Mondays) I face less administrative hassles in the long run. This is because there's nothing productive that can be done in that hour except administrative work. Submitting forms, replying to emails, returning library books are all things that otherwise fall by the wayside to your productivity, but this way I don't get into trouble or waste "good" time doing them either.
- tsally 17y ago
  Good point. Another option (as Randy mentions in his talk) is to schedule a "fake" class during the dead hour. Just go to the same spot in the library every day and work on the same class. Office hours are useful for this purpose as well.
  - Periodic 17y ago
    I sort of did this during my undergrad. But instead it was essentially 9-5 minus whatever classes I had. I would just spend any time not in class during the work day to work on class work unless I had every assignment done. It helped me get ahead and then I could just relax in the evenings because I knew I'd have time to work on things later in the week. In many classes it's much easier to do productive work in an hour than at most programming jobs. Programming jobs tend to be structured in terms of large projects/milestones, while classes tend to have smaller goals or problems on the problem sets that can be done in < 1 hour. And if all else fails, reading a text book for an hour can be quite productive, and it's nice to let the information settle in your brain before applying it anyway.

by tsally 17y ago

arjunnarayan 17y ago

Counterpoint: While I agree, I have found that when I have a little spacing between classes per week (say one hour between lectures on Mondays) I face less administrative hassles in the long run. This is because there's nothing productive that can be done in that hour except administrative work. Submitting forms, replying to emails, returning library books are all things that otherwise fall by the wayside to your productivity, but this way I don't get into trouble or waste "good" time doing them either.

tsally 17y ago
Good point. Another option (as Randy mentions in his talk) is to schedule a "fake" class during the dead hour. Just go to the same spot in the library every day and work on the same class. Office hours are useful for this purpose as well.
- Periodic 17y ago
  I sort of did this during my undergrad. But instead it was essentially 9-5 minus whatever classes I had. I would just spend any time not in class during the work day to work on class work unless I had every assignment done. It helped me get ahead and then I could just relax in the evenings because I knew I'd have time to work on things later in the week. In many classes it's much easier to do productive work in an hour than at most programming jobs. Programming jobs tend to be structured in terms of large projects/milestones, while classes tend to have smaller goals or problems on the problem sets that can be done in < 1 hour. And if all else fails, reading a text book for an hour can be quite productive, and it's nice to let the information settle in your brain before applying it anyway.