Computer Science
What it actually is
Computer science is the study of information: how it can be represented, transformed, and reasoned about. Programming is its lab technique — the way you make ideas run — but the subject itself is bigger: what can be computed at all, how to organise millions of lines of code so humans can still change them safely, how machines learn patterns from data, how to keep systems secure against people actively trying to break them.
It is a young field with an unusual property: the things you build are made of pure thought, and yet they run the modern world. Banks, hospitals, transport, communication — all of it now sits on software, which means computer scientists inherit both enormous leverage and real responsibility.
The degree teaches you to think in abstractions and then make those abstractions concrete and fast. It rewards precision: a program does exactly what you told it to, which is frequently not what you meant.
Where it branches
A day in the life
A working software engineer reads far more code than they write. A normal day: pick up a task, spend most of the effort understanding the existing system and why the bug happens, change perhaps thirty lines, write tests, then have colleagues review the change and argue about it — that argument is quality control, not hostility.
Around that sit meetings about what to build next, and the occasional genuinely absorbing deep-focus stretch that is the reason many people love the job.
As a student: lectures that feel like maths, programming assignments that consume weekends (the last bug always takes the longest), and the strange joy of a thing finally working at 1 a.m.
The degree vs the school subject
School computing is mostly "make a thing that works". A CS degree begins with why it works: discrete mathematics, proofs, data structures and algorithm analysis, computer architecture. Plenty of students arrive loving coding and are ambushed by how mathematical the first year is.
The reverse surprise also happens. People who never coded before university often flourish, because the degree teaches from first principles. Prior coding experience helps less, and mathematical comfort helps more, than most applicants expect.
Who thrives — and who doesn't
CS suits people with puzzle stamina — those who can be stuck for two hours, stay curious rather than frustrated, and feel the fix was worth it. Precision matters: careless-but-fast is a painful fit. You don’t need to have coded since age ten; you need to enjoy debugging, which is the actual daily texture of the field.
It goes badly if you want the prestige of "tech" but dislike sitting with hard abstract problems, or if vague, open-ended fiddly detail drains you.
Misconceptions
People thinkComputer science = learning to code.
ActuallyCoding is the tool. The degree is mathematics, algorithms and systems design — closer to applied maths than to a coding bootcamp.
People thinkYou must have been programming since childhood.
ActuallyUniversities teach from scratch. Mathematical readiness predicts success better than years of hobby coding.
People thinkAI means the field is about chatbots now.
ActuallyAI is one branch, and its serious work is heavy mathematics plus engineering. The unglamorous systems knowledge underneath is as employable as ever.
Where it leads
- Software engineering
- Machine learning / data science
- Security engineering
- Infrastructure and systems
- Quantitative finance
- Product management
- Founding or joining startups
- Research
Historically among the strongest degrees for employment, and still so — but the entry level has become genuinely competitive in recent years, and hiring runs in cycles. What separates candidates is evidence of building: internships and personal projects matter alongside the degree. The skills transfer unusually well across industries, which is quiet insurance most fields don’t offer.