I keep following the request because “it works” has never been enough for me.
I got into software to understand how things actually work, not just use them. That took me from full-stack web (React, TypeScript, Node.js, PostgreSQL) into running local models like Qwen through LM Studio and Ollama, and into C++, where I work through systems concepts to see what the machine is really doing.
It's also how I debug. My Discord bot once went silent for everyone while the model was thinking: one HTTP request inside an async function was blocking the event loop. A worker thread fixed it, and taught me code can look async and still not be. So I read what the layers underneath actually do, then publish a writeup.
On a team, I take ownership and follow through. I led the front end at Hack the Break 2026, where we placed Top 6 of 36 teams in 24 hours, and led backend and DevOps on SkillMatch with 105 of our 199 commits. Solo on Network Growth Assistant, I wrote 1,523 unit tests, because I'd rather prove something works than assume it does. You can count on me to ship it, and to explain how it works afterward.
I'm a BCIT student (88% average, graduating May 2027) looking for a co-op or internship in Vancouver, where code review is part of the culture. I want to learn how good teams build, test, and ship software, and I'll take on hard problems to get there.
What a hiring manager usually wants to know first, answered up front.
06 NEXT STEP
Have an interesting problem?
Open to co-op, internship and software roles in Vancouver, on-site or hybrid. Graduating May 2027. Tell me what you're building and I'll reply within two business days.