All writing

Essay2 min read

Twelve years on the job instead of university

Taking an internship straight after A-Levels in 2014, what working early taught me faster, and the bits I had to go back and learn myself.

Twelve years ago, two months after finishing A-Levels in Computing, Maths, and Physics, I turned down university and joined my own sixth-form school — Hurstpierpoint College — as an intern web developer instead.

I don’t think there’s one right path into software engineering — plenty of brilliant engineers I’ve worked with did CS degrees, and plenty didn’t. Looking back from twelve years in, though, skipping uni shaped how I learn and what I tend to build in pretty clear ways.

What working early gives you fast

My first job wasn’t toy assignments; it was a live school portal used by around 1,000 students and 300 staff every morning. When the daily check-in system broke at 8:30 AM, real teachers were stood waiting for it.

That kind of feedback loop teaches a few habits much quicker than lectures do:

  • You stop treating code as the end product. Nobody cared whether my PHP was clever; they cared whether registration worked during peak ten-minute windows and didn’t lose records.
  • You get comfortable picking up whatever stack the job needs. Over twelve years I’ve jumped from standalone PHP and Laravel at Hurstpierpoint, to agency web work and leading iOS in SwiftUI at Sonin (with a bit of Go and Kotlin on the side), to high-traffic Laravel and Vue at Tutorful, to partner APIs and AI tooling in TypeScript at Tillo.
  • You learn how teams actually ship. Code reviews, legacy migrations, rolling out tooling across four teams without wrecking everyone’s open branches — most of the hard parts of senior engineering are coordination and judgement, not syntax.

The bits you have to fill in yourself

Skipping a degree isn’t free, though. There’s a whole layer of computer science and lower-level systems work that day-to-day CRUD web development never forces you to touch.

If you don’t go looking for it on your own time, it’s very easy to spend a decade comfortably inside high-level frameworks without really understanding filesystems, memory, binary protocols, or how compilers work.

Looking at my own side projects from the last couple of years, almost all of them are basically me scratching that exact itch:

  • Building Petal in Rust and GPUI meant getting properly into macOS APFS clones, hard links, and getattrlistbulk.
  • Building OpenCharm meant writing dual-core ESP32-S3 firmware, DMA display flushes, and streaming I²S audio.
  • Writing az-lang in Go was just a fun excuse to build a small lexer, parser, and interpreter from scratch.

Would I do it again?

Probably, yes. Starting early gave me a massive head start on real-world engineering judgement, and nowadays if I want to go deep on Rust, embedded firmware, or audio DSP, nothing stops me from opening a repo on a weekend and figuring it out.

Learning on the job worked out well — as long as you keep picking jobs and side projects that make you slightly uncomfortable every couple of years.