Brandon Seokhyun Wie
Software engineer writing about backend systems, DevOps, and lessons learned building real products.
Backend engineer building production systems at scale — film school grad turned engineer, now leading backend at Moba. This blog collects what I've learned along the way.
Work
The Calendar That Remembers Everything
Sole-maintained backend from legacy to public launch — multi-account calendar sync, payments, and real-time updates across 7M events.
Public 3B architecture map
Sanitized system map for the 3B agent harness behind this site: layers, subsystems, decisions, and blog-series progress.
AISecOps Knowledge Platform
Zero Trust security for generative AI — 6 polyglot microservices (Python + Go + Rust + TypeScript), Kafka event streaming, hash-chained audit, and full LGTM observability on hybrid GCP + NAS infrastructure.
Recent Posts
See all 155 posts →WAF Allowlist Patterns
Block-by-default WAF approach using route allowlisting. Stronger security than
A Harness That Fixes Itself - And Prunes Its Own Fixes
The most expensive agent mistakes are not the dramatic ones.
Forward Links Only: A Zettelkasten Where Backlinks Are Computed
3B stores the link an author can maintain, derives the reverse edge later, and makes the struggle behind a note part of the knowledge itself.
Folder Is Destiny: A Six-Layer Information Lifecycle
3B lets folder placement decide retrieval, privacy, and staleness most of the time, then uses frontmatter overrides for the cases where physical location and...
Parallel Agents Without Collisions: Tasks, Worktrees, and Locks
Parallel agent work usually looks like a Git problem. Two sessions edit the same repository, one lands first, the other gets a conflict, and everyone learns...
Rules That Route Themselves: Frontmatter as the Loader
In 3B, YAML frontmatter is not decorative metadata. It is the routing language that decides which agent sees which rule, when, and in what shape.
Same Skill, Three Transport Physics
A skill can be authored once and still travel differently to each agent: Claude resolves canonical bytes, Codex reads a pinned adapter, and AGY splits native...
The Token Stack: Four Layers of Code Intelligence Without Re-Scanning
The easy answer to agent context burn is "add memory."
Three Gates and an Audit Log: HITL for an Agent Harness
The first version of an agent workflow usually has one safety rule: ask before doing something risky.
The Session Engine: /wrap, Clean-Slate Rollups, and a Cross-Session Buffer
Agent work does not fail only because the agent made a bad edit. It also fails because the next session cannot tell what happened.