About

I'm a systems-minded builder with a background in software development and enterprise architecture, and I'm most interested in the space where technology, data, and thoughtful design come together. I enjoy taking something that feels messy, inefficient, or unnecessarily complicated and figuring out how to make it simpler and more useful. I'm naturally drawn to organizing information, designing systems, improving workflows, and building tools that people can actually use. I'm especially interested in AI because it has dramatically lowered the barrier between having an idea and being able to build it. Rather than seeing AI as a replacement for technical skills, I see it as a way to turn ideas into working systems much faster.

I'm also passionate about health, fitness, and personal data. I've built my own personal analytics platform to bring together nutrition, workouts, weight, mood, journaling, and other aspects of my life in one place. What started as a simple way to track calories has evolved into a way for me to explore patterns and better understand myself over time. I enjoy looking at historical data, testing assumptions, building dashboards, and asking questions that I wouldn't be able to answer from memory alone. I'm particularly interested in the relationship between different parts of life like how nutrition relates to weight, how training relates to recovery, how circumstances affect mood, or what was happening around a particular period of progress. For me, the value isn't necessarily predicting what will happen next; it's having enough context to understand what actually happened.

At a broader level, I tend to think in patterns and systems rather than isolated events. I like connecting seemingly unrelated pieces of information, looking for recurring behaviours, and turning observations into something I can examine more objectively. I'm also comfortable being wrong. I would rather test an assumption and discover that my intuition was incorrect than protect a belief simply because it feels true. Whether I'm designing a software system, organizing information, analyzing data, or building something for myself, I tend to follow the same cycle: notice friction, understand the problem, design a better system, build it, observe what happens, and iterate. I'm happiest when I can work through that cycle continuously and leave something more useful, understandable, or organized than I found it.