3 ms·
At UW? No. You must log in at exactly 6am (preferably 5:58) on your registration day. Have your planned schedule in hand with all class codes and multiple backu
by brewdad 2y ago
At UW? No. You must log in at exactly 6am (preferably 5:58) on your registration day. Have your planned schedule in hand with all class codes and multiple backups. Assuming the system doesn't crash repeatedly, all of the required and/or popular classes will be full by 6:05.
Rinse. Repeat for the entire 2 weeks of registration.
- JohnMakin 2y agoThis is pretty much how it works at every school I've ever attended. It ended up driving me towards "hacking" by writing a bunch of scripts to register as fast as possible, taught me some basic networking in the challenges I faced while doing that, and occasionally grabbed me a seat in a class I normally wouldn't have. However, I think a lot of other students in CS were also doing similar, because it would never make sense how stuff could fill as fast as they did. As a result, sometimes I would have to beg to be allowed to take a graduate level course to fill a requirement, just because it had seats. Ended up working out for me, as one of those graduate professors ended up offering me a job in my 2nd to last quarter, but I wouldn't be surprised if such overloaded systems just brutally sabotage people's entire education.
- kelnos 2y agoIt's amazing how little things have changed. I was Cornell class of '03, and this is basically how we registered for classes (though the "system" was a Java AWT app rather than what I assume is now a website) 25 years ago. It was a miserable experience. There has to be a better way to solve this problem.