Operating notes from the quiet side of campus

The version of me that shows up in meetings is patient on purpose. The version that writes this page is the same person, just allowed to admit that I find beauty in well-labeled Moodle releases and WordPress multisite configs that survived a funding cycle.

HKUST stamped the engineer in first: Bachelor of Engineering in Computer Science paired with enough business coursework to convince me spreadsheets are morale devices. Copenhagen at DTU was the semester that taught humidity is optional and Scandinavian bike lanes spoil you for every other commute. Afterwards I chased problems that smelled like constrained budgets and brittle integrations—somewhere along the road I leaned hard into Learning Management Systems because they punish vanity and reward meticulous release notes.

The era at TWU refined my instincts—how to shepherd Moodle through enrolment earthquakes, coax WordPress multisite stacks into behaving during campaign traffic, translate vendor PDFs into something faculty can skim before class. I learned that empathy for instructors is inseparable from respect for uptime: if midnight exam support burns people out once, they'll remember it forever.

When I flirted with startups the tempo changed but the instincts didn't. Suddenly I wore product hats and recruiter hats before lunch, still debugging cache headers after dinner. The combination—university patience plus startup compression—left me allergic to hero launches without runbooks. If you cannot explain rollback, you are not ready to celebrate.

Faith is not a footnote. Sunday rhythm lives at the Vancouver Church of Christ, where I get reminded weekly that leadership is servanthood with receipts. That conviction bleeds into how I write documentation: anonymous heroics do not scale; shared clarity does.

Japanese practice is my contrarian hobby—slow, humbling, and wonderfully unrelated to ticket queues. It keeps me honest about being a beginner again, which is useful when a new instructor asks "why does the gradebook export look haunted?" and the answer is part SQL, part policy, part timing.

If you want the practical artifacts, wander back to the case studies, skim yomaru.dev, or watch me narrate experiments on YouTube. If you want human contact, email still works.