I like problems more than technologies.
Technologies change every year. The ability to sit with a hard problem, understand it properly, and build something practical out of it, that compounds. Everything on this site comes from that one habit.
How I got here
I moved to Canada to study computer science, and did what I always do in a new place: found the problems nobody was working on. Within two years that turned into building accessible course technology used by a thousand students, running the campus IT Club, and directing operations for a 250-person AI hackathon during Toronto Tech Week.
The projects followed the same pattern. Each one (a feasibility platform on census data, an exoplanet classifier on NASA archives, a drug-safety companion on FDA labels) started with a question I couldn't stop thinking about, not with a framework I wanted to try.
Alongside the engineering, three years of freight operations at The Home Depot taught me something no course did: how real systems behave under pressure, and how to keep showing up.
Understand first, build second
Every project on this site went through the same sequence: understand the problem, research what's actually needed, design, build, test, improve. When I skip a step, the work tells on me, the ETHOS case study documents exactly what happened when I trained models before auditing the data.
I write down trade-offs. I keep tests honest. And I'd rather say "I originally chose X, but switched to Y because..." than pretend the first plan survived contact with reality. It rarely does.
The human part
Away from a keyboard I'm usually mentoring someone, organizing something, or exploring somewhere new. Mentorship is the throughline, guiding an international student through their first Canadian job search taught me as much about communication as any codebase has.
- Building Zonalyze, a business feasibility platform, as my capstone.
- Completing a Bachelor of Computer Science (Honours) at Conestoga College, 3.74 GPA.
- Leading the IT Club and helping run GDG Waterloo events.
That's the person behind the projects.
If any of it resonates, a role, an idea, or just a good technical conversation, reach out.