About Me
Hey — glad you found your way here. Read on.
Origin story
I'm a lifelong technologist. My first steps into computing came in the early 1990s, before the internet had become part of everyday life in Australia.
I was lucky to grow up in a household with a computer. An IBM machine
sat in the entryway of our family home: a heavy power switch, a screen
flickering through its boot sequence, and eventually the familiar
C:\> prompt. It felt like a world of possibilities.
It was a DOS world. Windows 3.1 was the new kid on the block, software was built by wizards, games arrived on floppy disks, and the three-finger salute (Ctrl + Alt + Del) became a reflex. It is hard to imagine what we tolerated, but it made every discovery feel earned.
My dad set the wheels in motion. He was not a computer enthusiast, but he knew his way around one, and that was enough to make the machine approachable. Curiosity did the rest. I found BASIC and started learning what happened when I replaced passive use with instructions of my own.
Games added fuel to that curiosity. Before finishing primary school, I was repurposing discarded i486 and Pentium II machines, wiring them together with null-modem cables or cheap network cards, and hosting games of Command & Conquer: Red Alert for my brother and friends. Those machines were unreliable, underpowered, and endlessly useful as teachers.
By high school I was building my own computers and trying different programming languages. C++ was the one that made the pieces click into place. Like every intrepid young programmer, I decided I would build a game.
That early pattern never really changed: understand a system by building something with it, follow the failure until it makes sense, and keep enough technical depth to turn an idea into a shipped thing. The systems are larger now, and the work is increasingly about helping teams do the same, but the underlying motivation is familiar.
Engineering and leadership
My work sits at the intersection of technical depth and engineering leadership. I enjoy finding practical paths through complicated product and systems problems, then giving the people around the work enough context, trust, and support to move quickly.
Managing technical teams is where I thrive. I care about continued growth, clear ownership, and results that survive contact with the real world. I also intend to stay hands-on: two decades of coding have made software construction part of how I think, not a rung I wanted to leave behind.
Outside technology, the recurring interests are motorsport, family, gardening, and an unreasonable amount of reading. Learning is only useful when it changes what I build or how I lead, so I try to turn what I consume into experiments, tools, and better questions.
Currently
Senior Manager, Software Engineering at GoPro, based in Sydney, Australia.
My day to day is largely occupied with building and shipping product with a small team, obsessing over Kotlin Multiplatform, thinking about systems design, and reading an embarrassing amount. See my recent career experience for more.
Connect
I'm heads-down at GoPro, but always happy to compare notes with people working on engineering leadership, Kotlin Multiplatform, developer tooling, or systems design.