Thin hook manifest
Have the hook config file declare only *what events to subscribe to* and route every one of them to a single handler binary; keep all branching, transformation, and policy in that handler.
Open to NA SWE roles
I build the systems that make AI agents reliable in production.
Most engineering happens in the messy middle, where retries lose money and agents drift off-script. That's where I want to live.
5th-year CS + BBA student at the University of Waterloo. Across five SWE internships I've shipped payment infra, AI agents, geospatial pipelines, and dbt automations. I'm drawn to the space where systems meet people, where retries don't lose money and agents don't break in production. Mostly I like shipping things people actually use.
Where I've shipped.
Where I've studied.
Tools I reach for.
Things I've built.
A disk-based DB engine in Go with B+Tree indexes for O(log N) reads, crash recovery via copy-on-write and fsync, and a SQL parser supporting multi-table queries.
Full-stack daily journaling app with Google OAuth, localStorage draft auto-save, and chapter-level API caching; serves 40 active users.
Recent posts.
Have the hook config file declare only *what events to subscribe to* and route every one of them to a single handler binary; keep all branching, transformation, and policy in that handler.
A single append-only file where an autonomous harness records every task it could not automate, who handled it manually, and the condition under which automation could resume.