Backend engineer
I build backend systems that run reliably in containerized environments, mainly with TypeScript and Go. I'm especially interested in domain-driven design and event-driven architecture.
from request to reliable delivery
What I work with
I see technology as a tool for solving problems, and I choose it with operations and scale in mind.
Latest
A running record of lessons learned from design work and small experiments.
Every Kubernetes anti-pattern checker in a five-check harness assumed `---`-separated documents. Naming more than one resource in a single `kubectl get -o yaml` call wraps the result in `kind: List` instead — and every checker silently found zero resources to flag, which looked identical to a clean pass.
Argo CD's App-of-Apps proof lives entirely on the parent; Flux's dependsOn proof is declared by the child and unverifiable alone. Audit either tree without including its root, and both fail the same way — for what turns out to be the same underlying reason.
A scoring harness covers nineteen categories of Kubernetes deployment mistake. One of them — drift — can only exist after a manifest has already been applied, which an authoring benchmark structurally cannot produce or avoid. The honest fix was a permanent, documented ceiling, not a future version.
Live
An offline-capable PWA for tracking developmental milestones (2–36 months) across four domains, plus a growth log with percentiles from birth. Not a diagnostic tool.
Live
A daily digest of Korean economic and real estate news and market indicators, rebuilt every morning by a GitHub Actions pipeline with an open-source local LLM summarizing the day.
Live
Korean housing subscription notices ordered by how soon they close, alongside housing-related government benefits you can narrow down by region, income and age.