Hi, I'm building in public.
I'm a platform engineer. Day to day I write Go, build cloud infrastructure on AWS, and look after the platforms, pipelines and deployments other engineers rely on.
- Years in tech
- 9+
- Companies
- 6
- Roles
- 8
- Learning now
- C
I got here the long way round. I started in 2017 as an IT technician, then moved through security operations, systems engineering and support into DevOps and platform engineering. Years of keeping real systems running taught me what fails. Now I want to know why.
So I'm going back to the bottom of the stack and learning systems programming in C. This site is the notebook for that journey: the deep dives, the daily logs, the dead ends and the "oh, that's how it works" moments.
Where I've been.
From fixing hardware to running cloud platforms, 9 years and counting.
DAZN
Platform Engineer
NowOct 2025 – Present · 1 yr 2 mos · Full-time · Remote
Writing Go and building cloud infrastructure on AWS. Platform and DevOps work: the pipelines, deployments and internal platforms other engineers ship on.
- Go
- AWS
- Platform engineering
- DevOps
DAZN Bet
DevOps Engineer
Sep 2023 – Sep 2025 · 2 yrs 1 mo · Full-time · On-site
- Go
- Cloud Computing (IaaS)
IT Support Engineer
May 2022 – Sep 2023 · 1 yr 5 mos · Full-time
- Go
- Cloud Computing (IaaS)
LiveScore
Desktop Support Engineer
Mar 2022 – May 2022 · 3 mos · Full-time
- Problem solving
- Okta Identity Cloud
GIBFIBRE
2nd Level Junior System Engineer
Sep 2019 – Mar 2022 · 2 yrs 7 mos · Full-time
- Go
- Problem solving
1st Level SOC Engineer
Jun 2019 – Sep 2019 · 4 mos
- Problem solving
- Technical support
Netgear Business
IT Technician
Jun 2018 – Jun 2019 · 1 yr 1 mo
- Problem solving
- Technical support
System Services LTD
IT Technician
Oct 2017 – Jun 2018 · 9 mos
- Problem solving
- Databases
Where I'm heading.
Understand systems well enough to design them, then lead the people who build them.
- Now
Master systems programming
Learning C properly: memory, pointers, syscalls, concurrency and how the operating system really works. Maybe C++ after that, but C first.
- Next
Principal architect
Use that low-level understanding to design systems other teams build on: knowing why a system behaves the way it does, not just that it does.
- The summit
CTO
Set technology direction for a whole company, grounded in knowing how the machine works underneath, and build teams that can do the same.
What you'll find here
- Deep dives: long-form explanations once a concept finally clicks.
- Daily logs: short, raw notes on what I worked on and what broke.
- Finds: papers, talks, repos and articles worth your time.
- Projects: the code that comes out of all of it.