I build software that turns real data into something people can actually use — from the screen someone taps to the logic quietly running behind it.
I like building things that actually do something with real information, not just display it. Across my projects, that's meant taking live market prices and turning them into a dashboard that can place trades on its own, taking satellite images and turning them into readable maps of crop health, and taking someone's income and spending and turning it into a clear picture of their financial health. In each case, the hard part was never just the interface — it was making the numbers underneath trustworthy: getting the calculations right, handling messy or incomplete data without breaking, and making sure the whole thing still worked when I came back to it months later..
That habit of caring about the whole chain, not just the part people see, started during my internship, where I built page elements that had to look right on every browser and screen size, and connected them to the backend so the data moving between them actually made sense. I tested and fixed real issues in a live application rather than a practice one, and I carried that mindset into my own projects since — I set up automatic checks that test my code before it ships, and I use Docker so a project runs the same way on any machine, not just mine...
- Building full-stack AI features on watsonx Workshop at IBM
- Going deeper on low-level systems programming, closer to the hardware
- Finishing Honours CS at Ontario Tech (President's List, Dean's Honours)