When I was fifteen, I broke every computer in my school. I wasn’t trying to. I was just exploring — poking at the system to see what it would let me do — and it turned out it would let me do far too much. I nearly got expelled for something I didn’t fully understand I’d done.
I think about that a lot, because it’s the whole story in miniature.
Curiosity is the engine
I’ve been obsessed with computers since I was a kid. I built my first website young, then a streaming site at fourteen, then apps, then games in Unity that never shipped. The thread isn’t any particular technology — it’s the compulsion to open the box and find out how the thing actually works.
That compulsion is also where a security mindset comes from. You don’t learn how systems break by reading about it. You learn by breaking them — ideally yours, on purpose, before someone else does it to you by accident.
The detour
After my diploma, Covid-era burnout pushed me away from code entirely. I spent three years in music — sound engineering, composition, Logic and FL — partly to find out whether computers were really the thing, or just the thing I happened to be good at.
They were really the thing. In 2023 I came back, this time going deep on iOS and on how computers work underneath the abstractions. Now I study every day. I’m disciplined about it in a way fifteen-year-old me would find hilarious.
Where this goes
I build software for real companies and, since 2025, for my own. But what I’m chasing isn’t a title — it’s becoming an exceptional engineer, the kind who understands systems deeply enough to build and break them, and who keeps the security lens on the whole time.
Build, break, rebuild. That’s been the loop since I was a kid. I don’t plan to stop.