Early on, we talked about the twice yearly pain of bidding for modules. Once you secure the modules that you want, there is yet another pain: balloting for tutorial slots.
Science and engineering students have it quite stressful. Not only do most lectures have 2 slots, you will also have weekly tutorials as well as labs that can be two to three hours. With some modules that have poor choices or if you happen to have a combination that has tutorials and lab clashes with each other then with little options, its a worry that you might have to go for many lessons at a long stretch or run from faculty to faculty. One or two breadth modules in different faculties is managable. However CEG students need to take both CS and EE core modules, and that requires running from COM1 / COM2 to E5 or E4. The route from computing to FoE is uphill. After the run, you’ll declare NUS as the national university of stairs.
Balloting for tutorial slots
Balloting is simple. You first select any of the avaliable tutorial/lab slots and then proceed to rank your preference for each slot. The ranking is not done per module but is done for all the modules at once. Therefore it is not recommended that you rank the same module consecutively. Unless everyone seems to like that slot, you’ll probably get it. The balloting system is meant to allocate the slots by random selection if they are over subscribed. There will be enough tutorial slots, its simply a matter of preference vs need but the system does not differentiate it. A preference starts to become a need if you have say two consecutive different tutorials at different places or your schedule configuration is such that you have little tutorial options.
4-Day week or less
What everyone hopes to achieve is the 4 or 3 day week. Its near impossible to achieve for engineering students. Arts students can achieve this with some luck and good planning. In CEG, most modules for year 1 and 2 are pre-allocated and hence you’ll have almost no control over your schedule until year 2 when you do all the tutorial and lab bidding. Unless you can seem to produce all your work and study within the working week, you will invariably spend your weekends and free time burning away at the keyboard trying to get that A on code crunch, make that recursion work or fill up the .cpp files with lines of code for that project.