Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's that, yes, but I think there's a point to be made for workload. I remember back in college all the courses would inevitably pile the workload on at the same time.

Around the same 2 weeks during a semester the profs will load up on all the projects, labs, and other must-dos, across all your courses. Taken separately these workload increases are modest, but as a whole you literally start running out of time.

My coping mechanism back then was to strategically not do some of these things, but then again my only intention going to school was to get a piece of paper that would unlock the Magical HR Gates at companies. My GPA isn't exactly great.



>>Around the same 2 weeks during a semester the profs will load up on all the projects, labs, and other must-dos, across all your courses. Taken separately these workload increases are modest, but as a whole you literally start running out of time.

At least for me, this became an issue only if I didn't do the homework assignments and study the class notes. What would happen is that we would get a large project, and I would realize that I didn't even have a firm grasp of the material. So I'd have to work two or three times as much, first to understand the prerequisite subjects, and then start working on the project itself.

After I figured this out and started to study regularly, projects started to become progressively easier, and as a result took less time. Even when professors loaded up on all of them within a short period of time, I could knock them out quickly because I was already very familiar with the subject.

It's like picking up a new programming language. There's the learning curve of the language itself, and then there's the learning curve of all the tools. But if you are already familiar with the tools themselves, you can learn the language much faster and get projects done much more quickly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: