Go on Jamal Yusuf

The Boring Go Layer Between Your RAG Demo and Production

Wed, 17 Jun 2026 00:00:00 +0000

RAG demos are seductive. Chunk a PDF. Embed. Retrieve. Watch the answer sparkle. Applause. Next slide.

Production RAG is a pipeline problem — documents that change, access policies that differ by team, embeddings that stale, audits that ask where a paragraph came from three quarters ago. The demo never shows that part. The on-call engineer lives there.

I keep choosing Go for the unglamorous middle between source systems and vector indexes. Not because Python cannot embed. Because operations is a language choice too.

Validating Agent Outputs in Go Before They Touch Production

Sun, 14 Jun 2026 00:00:00 +0000

An agent that sounds right is the most dangerous kind of wrong.

I have seen it in healthcare workflows — confident JSON, clean prose, a downstream system that accepts the payload and only screams twenty minutes later when reconciliation fails. The model did its job. The system failed to treat probability like probability.

In Go, I fix that with a boring layer between the model and the world: validate before side effects. Always.

Context Is the Kill Switch: Go, Cancellation, and LLM Timeouts

Wed, 10 Jun 2026 00:00:00 +0000

The first time I watched an agent runaway eat a month’s inference budget in an afternoon, nobody blamed the model. They should have blamed the missing kill switch.

The model kept going because nothing told it to stop. Tool calls chained. Retries compounded. Goroutines — or their equivalent — waited politely for a provider that had already left the building.

In Go, the kill switch has a name: context.Context. And I think it is the most underrated tool in production LLM orchestration.

Why Go Remains the Best Language for LLM Orchestration

Sun, 03 May 2026 00:00:00 +0000

I have orchestrated LLM workloads in more than one language. Python gets you to demo fast. Go gets you to sleep — or at least to on-call with fewer surprises.

That is not ideology. It is fifteen years of distributed systems scar tissue talking.

The concurrency advantage

Agent orchestration is not one request. It is dozens of concurrent flows — tool calls, retrieval hops, validation steps, retries with independent timeout budgets — all competing for resources while a human waits on the other end.

The Go Advantage for Production Agentic Systems

Wed, 10 Dec 2025 00:00:00 +0000

Agentic systems are distributed systems wearing a chat costume. The sooner you accept that, the fewer 3 a.m. pages you earn.

I have been building Go backends since 2011 — Kafka pipelines, membership APIs, payment flows, the unglamorous center of enterprise operations. When multi-agent workflows arrived, I did not reach for a new religion. I reached for the same primitives that kept the event backbone alive.

Why Go for agent orchestration

Multi-agent workflows are coordination problems: fan-out, join, timeout budgets, partial failure, human escalation. Go’s concurrency model — goroutines, channels, context cancellation — maps to those problems without pretending parallelism is free.