What Three Years of a Computing Degree Actually Taught Me
An honest look at the fundamentals that stuck from my BSc — and the gap between coursework and shipping something real.
Where it started
I started my BSc (Hons) Computing at Itahari International College — affiliated with London Metropolitan University — knowing almost nothing about programming. Three years later the thing I value most isn't any single language. It's a way of breaking problems down and the confidence that I can learn whatever a project needs.
This is a short, honest account of what actually stuck, and where the coursework stopped and real building began.
The fundamentals that carried over
The early modules moved through a deliberate order, and in hindsight each layer mattered:
- Programming basics with Python and Java — variables, control flow, and thinking in functions before thinking in frameworks.
- HTML and CSS — structure and layout, and learning that "it works on my screen" is not the same as "it works."
- JavaScript — the first time a page reacted to a user instead of just sitting there.
- SQL and database design — normalisation, relationships, and writing queries that don't fall over as data grows.
None of this is glamorous, but it's the part I lean on every day. Frameworks change; knowing how a relational schema should be shaped does not.
The jump from coursework to real projects
Textbook exercises have a right answer printed two pages later. Real projects don't, and that gap is where I learned the most.
The clearest example was my final-year project, Kick Up Futsal — a multi-role booking platform with separate dashboards for players, futsal managers, and admins. The coursework taught me how a REST API should be structured. Building the booking flow taught me what happens when two users try to reserve the same slot at the same time, and why you handle that on the server, not the client.
I also built an IoT bus-tracking system that connected Arduino sensors to a live web dashboard through the Google Maps API. That project forced me to reason about data I didn't fully control — sensor readings arrive late, out of order, or not at all — which no lecture had prepared me for.
What I'd tell someone starting the same degree
A few things I wish I'd internalised sooner:
- Build past the assignment. The brief is a floor, not a ceiling. The extra features you add for yourself are what you'll actually remember.
- Read error messages properly. Most of them tell you exactly what's wrong once you stop panicking and read the line number.
- Learn the database layer well. It's less fashionable than front-end frameworks and it ages far better.
- Ship something end to end. A small project that's actually deployed teaches more than three half-finished ambitious ones.
Where it leaves me
The degree gave me a foundation; the projects taught me how to use it under real constraints. Since graduating I've kept building on it — picking up React, Next.js, and a production backend stack — and the same approach holds: understand the problem, choose the right tool, ship, then improve. That's the part of the education that wasn't on any syllabus, and it's the part I rely on most.