[ Services ]
Senior engineer. Occasional advisory work.
I occasionally help small teams reason through backend reliability, Go performance, distributed systems, and production AI workflow design.
If the scope is technical, specific, and compatible with my availability, feel free to get in touch.
[ Areas_I_Can_Help_With ]
- Go backend performance
- gRPC / NATS / Redis architecture
- Production AI workflow reliability
- Observability, latency, retries, and failure modes
- Architecture review for small teams
[ Recent_Writing ]
A few representative pieces.
Claude Code Source Leaked: 5 Hidden Features Found in 510K Lines of Code
What Anthropic's leaked agent source reveals about how production AI agents actually work.
Claude Code · ArchitectureThe 1,421-Line While Loop That Runs Everything
10 steps per iteration, 9 continue points, 4-stage compression, streaming tool execution.
Claude Code · Context EngineeringThe 5-Level Compression Pipeline Behind 1M Tokens
How Claude Code keeps sessions alive past the context window without losing fidelity.
AI Agents · ReliabilityThe 90% Problem: Why Most AI Agents Are Still Broken
The reliability gap between “works in the demo” and “works on Tuesday at 3am.”
AI Infra · ObservabilityObservability and Billing for AI API Calls: A T-Shaped Architecture
Why your AI bill is 3-5x what your token meter says, and the architecture that fixes it.
Go Runtime · ConcurrencyNode Turns Waiting Into Events. Go Moves Context Switching Into User Space.
Stackless vs stackful coroutines, function color, and what the unit of scheduling actually is.
Distributed Systems · PatternsRPC vs NATS: It's Not About Sync vs Async — It's About Who Owns Completion
The framing that separates teams who debug at 3am from teams who don't.
Go · ProfilingGo Profiling in Anger: pprof, Escape Analysis, and Inlining Without Magic
The exact tools and reasoning chain I bring to Go performance work.
[ Get_in_Touch ]
A short note about what you're working on is the easiest way to start.