First Year Survival Guide
What to expect, what matters, and how to stay on track from day one.
What to expect
CS is not "just computers." It's problem solving, logic, and discipline — the computers are just the tool. First year is designed to give you a foundation across multiple areas at once: mathematics, programming, databases, networking, and systems.
The pace feels slow at first — week 1 and 2 might feel almost too easy. Don't be fooled. The workload compounds fast, and by mid-semester, multiple deadlines will hit at the same time. The hardest part of Year 1 is not intelligence — it's consistency.
Why it feels overwhelming
If you're feeling overwhelmed, it's not because you're in the wrong degree. It's because:
- It's a new environment with new people, new independence, and new expectations all at once.
- You're studying 5+ different subjects simultaneously, each with its own logic.
- You don't know yet what actually matters — so everything feels urgent.
- You're genuinely learning how to learn again. High school study habits often don't transfer well to university CS.
This is normal. Almost everyone feels this way in weeks 1–4.
Don't panic about this
- Feeling lost in week 1–3 is completely normal. The people who look like they know everything are mostly performing confidence.
- Everyone struggles in math and programming moments. There will be a topic that clicks for some and doesn't for others. That's the subject, not your ceiling.
- You're not behind just because someone talks big. Half the people loudly discussing code in week 1 will be scrambling by week 6. Focus on your own progress.
The 3 modules to take seriously from day one
Mathematics for Computing (MCI)
This is pure logic — Boolean algebra, combinatorics, sets, number systems. It's heavily practice-based. If you don't do exercises regularly, it will catch you off guard in tests. Do problems daily, not just before assessments.
Introduction to Programming (PRG)
This is about learning to think like a programmer. The language is secondary — the skill is breaking problems into steps. Don't just watch examples. Type the code yourself, make it break, fix it. That's how you actually learn this.
Database Fundamentals (DBF)
SQL and data logic. It seems straightforward early on, but gets layered quickly — joins, normalization, constraints. Practice writing queries from scratch, not just reading them. The difference between someone who "gets" DBF and someone who doesn't is almost always hands-on time.
Easy modules can still trip you up
Some modules might feel light in terms of content, but they come with assignments, portfolios, or group work that has real weight. Don't let "easy" make you complacent. Missing low-effort marks is the most avoidable mistake in first year.
- Read assignment briefs carefully — the instructions are usually more specific than they look.
- Deadlines in "soft" modules still fail students. Treat every deadline the same.
Recovery plan if you fall behind
If you've missed a few weeks of content, here's the approach that actually works:
- Don't try to catch 6 weeks in one day. It won't stick and you'll burn out.
- Catch up in layers: first understand the topics broadly, then do practice questions on each, then tackle past exam questions.
- Minimum daily effort beats weekend panic sessions every time. Even 45 minutes a day will compound faster than you think.
- Ask for help early — lecturers are more willing to assist students who show up before the test, not after it.
Quick checklist
- Attend lectures or watch/cover the content on the same day
- Do a small practice session daily (even 20 minutes)
- Keep up with smaller assignments — don't let them pile
- Ask questions early — week 2, not week 9
- Know what your assessments are and when they're due