An honest picture of what a computer science degree really is before you start — problem-solving over memorization, why it's not just 'learning to code', and how to set the right expectations for four years.
Most people arrive at a CS degree with one of two wrong pictures: "this is a coding bootcamp with exams," or "this is advanced maths I'll never use." Both cause real damage in first year — the first leads to memorizing syntax without understanding, the second to giving up on fundamentals that turn out to matter enormously. Getting an accurate picture before you start is the cheapest advantage you can give yourself.
What computer science actually studies, why "learning to code" is only a small part of it, and what mindset makes the next four years work in your favour instead of against you.
At its core, computer science is the study of how to solve problems systematically — how to break a large, vague problem into precise, solvable pieces, and how to reason about whether a solution is correct and efficient. Programming languages are just the tools you express solutions in. Tools change constantly; the underlying problem-solving skill transfers to all of them. This is why "which language should I learn first" is the wrong question — the language barely matters; the thinking is everything.
Coding is to computer science what writing is to literature: essential, but not the point. A CS degree also covers how computers work underneath the code, how to structure data so problems become tractable, how systems talk to each other, and how to reason about correctness. Students who skip the theory tend to hit a hard ceiling in third year and in interviews, where exactly that theory is tested.
If there's a single concept that unlocks computer science, it's abstraction — hiding complexity behind a simpler interface so you can build bigger things without holding every detail in your head. A function is an abstraction. So is a file, an operating system, and the internet. Almost everything you learn is another layer built on the ones below. Once you see your degree as "layers of abstraction," a lot of confusing topics suddenly connect.
You will feel lost sometimes — that's normal and not a sign you don't belong. Concepts click on a delay; something baffling in first year often becomes obvious in second once you have more context. The students who thrive aren't the ones who understand everything immediately; they're the ones who keep going when they don't. Play the long game.
Get your tools working first — see Setting Up Your First Development Environment. Then read How to Think About Your College Years.
Part of: Incoming Students