SELECTED WORK / EVIDENCE
Professional production work, client delivery, and owned products. The technologies vary; the recurring work is to define contracts, isolate ownership, handle state and failure, and make the result operable.
Production push and SMS delivery handling 1M+ push notifications and 50K+ SMS messages per day, with five SMS providers, retry behavior, delivery-state tracking, and operational troubleshooting.
An existing operational platform I took over end-to-end. A 12-tab user detail view was changed from blocking full-page loading to independent lazy-loaded tabs, while sensitive state changes use layered revalidation.
ETL and calculation workflows for complex store, product, team, and item-specific incentive rules, including explicit handling of incomplete, malformed, failed, and orphan records.
An integration layer connecting frontend requests, DB APIs, frequently changing computation modules, result artifacts, and persistence. The architecture isolates team-owned code behind explicit execution boundaries.
Extended an existing ASP.NET Framework portal for a large residential common-area BMS. Vendor-collected Modbus data lands in a database; the application adds electricity-cost estimation and equipment-point trend analysis.
Born from a real live-production problem: teams exchanging console and show files through filenames, dates, and version suffixes with no clear authoritative copy. PatchGrid is now a production SaaS used by dozens of users.
A substantial greenfield Go + React system under active development. Implemented foundations include a PostgreSQL cloud core, SQLite edge agent, multi-tenant IAM, WAMS, roster/scheduling, People, Check-Ins, Groups, notification workflows, CI, deployment tooling, and real-database integration tests.
Real deployments integrating building systems beyond their vendor software: Modbus TCP for Daikin HVAC and a reverse-engineered proprietary UDP protocol for Lite-Puter lighting control.
A working LINE-to-LLM prototype with a separate backend, JWT authentication, persistent chat rooms and messages, and Firestore. The engagement stopped before production when API operating cost changed the business case.
A prototype motivated by the native iOS app being too broad for musicians: expose only a user's own monitor mix and a deliberately limited control surface.