What I Wish I Knew As a First Year Computer Science Student
Being a First Year at McGill isn’t easy. Between recovering from Frosh and figuring out what the significance of samosas are around this place, there’s a lot to unpack. So, whether you’re just debating a Computer Science degree, or are already set on it as your academic path, here are a few things that might help you.
1. Your Professor Matters
Because the majority of courses you will take in your first year are absolutely huge, I mean 300 students huge, the way in which the professor communicates and teaches the course content is crucial. This does not necessitate that one professor is better than the other, but simply that different students have different learning styles.
If you aren’t compatible with a professors grading scheme, for example, it may be best to take the course next semester when there’s a different prof leading the course. If you know that final exams that count for 75% of your grade are overwhelming for you, then try to find professors who weigh class projects more.
One way to figure out if a professors teaching style is for you is by going on ratemyprof and reading through reviews. Remember, though, that reviewers are usually motivated to write by extreme perspectives – either very positive or negative – and therefore the reviews may not be the most accurate. Otherwise, you can peep the syllabus of the course during add/drop and confirm how intense the workload is by speaking to other upper years about their experience with the prof.
2. Not All CS Courses Are Like COMP202
If you love problem solving, chances are you will thrive in COMP202. The projects are stimulating and, dare I say, fun. It’s therefore easy to get carried away and assume that the rest of CS will pretty much be an extension of the content you learn in the course.
COMP202, however, is more so centred on the syntax of Python and general logic of programming. Contrasted with the theory-heavy, Math-involved upper level courses, it truly does not compare. In fact, some CS courses do not contain any programming at all and rely mostly on non-language specific code (i.e pseudocode). COMP250 might be a better way to judge whether or not completing a full CS degree is for you. This is due to the class’ emphasis on algorithms, which you will use for almost every course to follow.
3. Most CS Projects Cannot Be Finished In A Day!
We all have success stories of defeating our procrastination and pulling an assignment together last minute. Starting CS projects right before deadlines and completing them on time, however, is a whole other beast. Depending on the professor and the class, assignments can take a few days (or more) to finish. My personal method is to start the project exactly one week before the due date. If I finish it early then, great, I can move onto other things and be stress-free.
4. If You Can’t Resolve a Bug, Leave it and Come Back Later
Here’s two deadly words: “Runtime Error.” That glaring red message will have you rolling in bed at night, staring out the window, or even calling your Mom, desperately, to get some words of affirmation. Not really (actually, yes).
When that happens, it’s best to put the coding aside and do something else. Programming tunnel-vision is a very real thing and taking a step back to gain perspective will uncover different angles of approaching the issue. You might also realise that the solution you’ve been working on is harder than it needs to be. So, when you think you’ve hit a dead end, go get a coffee, start work for another class, or maybe even take a long, well-deserved break.
5. Take Advantage of CS Resources
While CS may appear intimidating, always remember that there are resources out there to help you. Here are a few you should take note of:
· CSUS and their Helpdesk in particular
· Math Burnside Helpdesk
· McGill SubReddit has some good information, for example this thread
And feel free to ask us questions on our Facebook page, where you can also find events to get involved with the CS community at McGill!
