The first week of the term is over, and it’s been the busiest first week I’ve ever had in my four semesters in school. Most of my time has been taken up by a single module, CS3216 (and quite expectedly so), and that’s mostly because it’s easily the only module I’ve been passionate about. I don’t foresee being any less busy in the coming weeks, so I’m pretty much banking on my time management skills to get me through unscathed.
I think it’s interesting how I ended up taking a module which quite frankly wasn’t anywhere near my academic roadmap until two months ago, and even then it was because one of the most awesome people in the School of Computing was promoting the perks of the module and the professor to me. It piqued my interest somewhat, and I applied for it after the examinations anyway, but in my mind I doubted I’d be taking it because I wouldn’t have been able to fit the module anywhere into the plans that I had made with the inclusion of NOC Silicon Valley.
Failing my calculus module last semester changed all that, and having to retake that painful module meant that I would have to all but give up my ambition of doing a double minor. I have additional modular credits that I still need to cover for Unrestricted Electives, and when I realised I was accepted for CS3216, a thought popped into my head that said ‘Why not?’.
CS3216 Software Development on Evolving Platforms is pretty much the unmodule of NUS, with a workload that is infamously heavy and past cohorts of brilliant students. It defies the structure of most modules, having no exams and no bell curve, and an inherent flexibility that borders on controversial. I was pleased to find out that CS3216 doesn’t lay claim on the intellectual property of the projects, and heartened to know that there were practically no boundaries in this module.
In spite of its attractiveness, I was still pretty torn about whether to take this module, even up until a few days before school. CS3216 seemed like a gem of a module, something even rarer than an interesting lecturer, and to not take it seemed a foolish choice. Yet, the advice given by some of my friends against me taking this was sound, and more importantly I had a CAP score that was screaming for attention. I could, after all, just find an easier module to take to fulfill the four modular credits.
Against all logic and the fear of a declining CAP score, I decided to go ahead with it. But unlike most people who are taking this module, I’m not taking it to learn how to work with people, learn programming (except Facebook development, maybe) or for the challenge. If I really wanted a challenge, I’d try to do a double degree in Engineering and Math, and take seven modules a semester. Anyhow, I examined my motivations for taking CS3216, and came up with the following three reasons:
The People. The strongest pull factor of this module is undeniably the talented cohort it attracts. I’m looking forward to networking with like-minded entrepreneurs, and well, just getting to know some of the most awesome and motivated people in the school.
The Module. If anybody asked me what my favourite module in school was, at least I’d have something to say.
The Decision. I’m most likely going to have to make a very important decision this year regarding NOC, and I’m really, really hoping that I’ll be able to find my answer talking to people from this module. I worry about this decision more often than I’d like to.
I’m really curious as to what my thoughts will be regarding this module at the end of the semester. I doubt I’ll regret taking this module, and the rush of adrenaline and exhilaration so far has got me pretty excited about the rest of the school term. I feel more motivated than before, more driven, and hopefully I’ll be able to make up for the failings of last semester. Somehow, despite my general cynicism towards academia, this feels like a good time to be in school.












