I dive in first and figure out the tools as I go. My work is in computer vision and on-device ML, but the curiosity goes much wider than that. I like understanding how things work at the level below where most people stop, and building things that actually matter to me.
Most of my life I've been a pattern finder. Give me something new and I'll have a mental map of it before I've read the manual.
Professionally I work in computer vision and on-device ML. For the past few years that's meant being part of a small team building a real-time golf shot analysis system with no prior art to reference. Every component had to be figured out from scratch. It was a hard problem and it got solved.
Outside of work, the same instinct takes over. What started as a small NAS slowly turned into a full self-hosted network. I run it for data privacy and control, but the deeper reason is wanting to understand how the internet actually works at a granular level. How systems talk to each other, where things break, what's happening under the hood.
When in doubt, dig deeper. What does the physics actually look like? How does the network actually decide? That curiosity is what drives everything.
Turning a phone into a precision instrument that competes with hardware costing thousands of dollars.
Professional golf monitors use radar arrays and dedicated sensors and cost upwards of $5,000. The goal was to match that capability using just an iPhone camera, computing ball speed, launch angle, spin, and carry distance in real time on-device.
There was no existing work to build on. No models to fine-tune, no datasets to train from, no papers to reference. As part of a two-person team, every component had to be designed from scratch: the neural networks, the physics engine, the camera calibration pipeline, the evaluation framework. Every design decision came from experimentation and measurement.
Getting it accurate enough to compete with dedicated hardware was a hard problem. It got solved.
A local-first, privacy-focused journaling app with AI-powered insights. Rich markdown editor, voice transcription via Whisper, mood analytics, semantic search, and weekly reflections.
GitHubA month-by-month net worth simulator. Model income and expense streams, investment buckets, and loans, with interactive charts and JSON import/export. No backend.
GitHubSelf-hosted personal expense tracker with multi-account support, investment tracking, analytics dashboards, and 7 colour themes. Data lives in a portable .xlsx file, not a database.
GitHubStarted as a homelab documentation project and grew into a full portfolio. Interactive infrastructure diagram, machine catalogue, live uptime status, self-hosted on my own VPS.
View LabThree machines, a private WireGuard mesh, and 30+ self-hosted services running at home. Part practical, part curiosity. Understanding how things work by running them yourself.
A homelab is personal infrastructure you run at home. Instead of relying on cloud services like Google Drive or Netflix, you run your own versions on hardware you own and control. For me it started as a storage experiment and became something much bigger: a way to understand how the internet actually works from the inside.
Interactive infrastructure map. Click any element for details. Hover a legend item to highlight related components.