About
I build the part that has to keep running.
The interesting problems show up after the model works: what it costs to serve, what breaks under bursty traffic, and what the agent actually retrieved.
I'm Matthew Hong, an AI engineer in Taichung, Taiwan, with a backend background in Go. Most of my work is the infrastructure around AI systems: the serving path, the agent's memory, and the instrumentation that says what actually happened.
I did not start in software. I studied financial engineering and actuarial science, worked as a financial analyst and an actuarial consultant, then as a data analyst at a precision-manufacturing plant, where I replaced the paper inventory and procurement workflow with the factory's first ERP system. That got me moved into software, and I have stayed there since: backend for a computer-vision safety platform running on cloud GPUs and Jetson edge devices, then Go services with a hexagonal architecture and a full OpenTelemetry, Prometheus and Grafana stack.
Alongside that I finished a master's in computer science at National Chung Hsing University. The thesis benchmarks three ML serving architectures under CPU limits; the second study led to batch2go, an open-source Go proxy for isolating where batching happens. Today I work as an AI engineer on taidle, a knowledge-base engine that agents query over MCP. What I learn on the way ends up on this site rather than in a notebook.
Experience
uber/fx, isolated schemas per domain module, raw SQL repositories. Built the observability stack end to end — OpenTelemetry Collector into Prometheus and Grafana, Tempo tracing, container and connection-pool metrics.