Skip to content
The blog

Written after the deployment, not before.

Essays on AI architecture, strategy and the org problems in between. Heart what’s useful, argue with me in the comments.


Mar 06, 2026

LLM11 min read

Failover Amnesia: Why Your LLM Chatbot Forgets During an Outage

Your application successfully fails over to a backup LLM provider during an outage, but your user's conversation is lost. This article explains why stateless failover breaks the user experience and details the stateful abstraction layer required to preserve conversational context, making your AI resilient in a way that users actually notice.

A chatbot icon with a broken connection and a question mark.

Feb 17, 2026

llm caching13 min read

Cut Your LLM Bill by 70%: A Guide to Four Caching Strategies for 2026

Explore four essential caching layers for LLM applications—prompt-prefix, full response, retrieval, and semantic—that can cut costs by up to 70% and serve responses in milliseconds. This guide covers the mechanism, risks, and metrics for each, plus when caching is the wrong choice.

Abstract graphic with overlapping colorful circles and lines, suggesting data flow and cost savings.

2 reads

Feb 10, 2026

llm-as-a-judge13 min read

Your LLM Judge's Secret Drift: Why 80% Agreement Isn't Enough

LLM-as-a-judge provides scalable evaluation but suffers from silent drift as models and rubrics change. This guide explains how to use a human-labeled holdout set to calibrate your judge, diagnose regressions, and prevent your evaluation system from misleading you.

Abstract scales with a judge icon and a downward trending graph.

1 reads

Feb 03, 2026

LLM11 min read

How to Log Your LLM: Unlock 99% Automation With Better Data

Traditional logging can't tell you if your LLM is getting worse. This article details the essential fields to log—from costs to verdicts—to debug silent failures, track quality, and automate up to 99% of your AI-driven workflows.

Abstract illustration of data streams flowing into a stylized brain icon.

1 reads

Jan 19, 2026

LLM12 min read

The 100x Cost Gap: When to Replace Your LLM With a Simple Rule

A single powerful LLM is often the most expensive and least reliable way to answer simple questions. This article explains how to build a routing layer that uses deterministic rules for simple queries, saving money and improving reliability, while reserving expensive models for the complex tasks they were built for.

A stylized circuit board with a glowing brain icon at its center.

Jan 06, 2026

ai agent12 min read

The $12 Agent Task: Why Production AI Needs a Harness, Not a Loop

Most AI agent demos are built on a simple loop that is too expensive and unreliable for production. Real-world systems use a "harness" architecture with structured workflows, checkpoints, and budgets to create agents that can survive contact with reality.

A stylized circuit board with a glowing red loop and a sturdy, structured harness.

1 reads

Dec 23, 2025

enterprise AI11 min read

The GenAI Divide: Why 95% of Enterprise AI Projects Delivered No Value

In 2025, enterprises spent $37 billion on generative AI, yet a stark "GenAI Divide" emerged. A landmark MIT study found 95% of projects failed to deliver any business value, revealing that success depends not on model quality, but on organizational strategy.

Abstract digital network with glowing nodes and a dark, fragmented background.

Dec 04, 2025

llm cost12 min read

Your Retry Loop Is a Time Bomb: From a $50 API Call to a $5,000 Bill

A simple retry-on-failure wrapper seems harmless, but in AI agent systems, it can lead to silent cost overruns and cascading failures. This article explains why, and how to build resilient, cost-aware error handling using techniques like total budget caps and structured escalation ladders.

Code snippet showing a three-line retry wrapper with a red warning symbol.

2 reads

Nov 18, 2025

Fixing Your Recurring Outage: Ask for a Schema, Not for JSON

Stop asking LLMs to "respond in JSON" and hoping for the best. Schema-constrained generation eliminates parsing failures and retries by forcing the model to produce valid output, token by token.

A server rack with a glowing red alert light and a broken circuit diagram.

1 reads

Nov 12, 2025

Prompts Are Production Code: Version Them Like It

A 2025 industry survey found that 30-40% of AI development time is spent on prompt engineering. This article explains why treating prompts as versioned, deployable artifacts is the key to reclaiming that time, improving reliability, and shipping faster.

Team members collaborate around a whiteboard with AI-related diagrams.

1 reads

Nov 07, 2025

The 1M Token Budget: Why 1 in 10 Queries Fail at Scale

Large context windows are not a free upgrade; they are a budget with steep costs in money, latency, and accuracy. This article explains the three hidden costs of long context and provides a framework for deciding when to use it.

A stack of coins with a question mark on top.

1 reads

Oct 29, 2025

llm evaluation10 min read

Your First Eval: Build a 30-Example Test Set This Afternoon

Stop building elaborate evaluation frameworks and start measuring model quality today. Learn how to build a small, effective 30-example evaluation set from real traffic in a single afternoon.

A person's hands typing on a laptop with a graph on the screen.

2 reads

Oct 17, 2025

rag12 min read

Chunking Is a Retrieval Decision: Up to 9% Recall Is on the Line

Most RAG systems fail due to a single, overlooked setting: chunk size. This article explains how rethinking chunking as a dynamic retrieval parameter, not a static preprocessing step, can boost recall by up to 9% and why the optimal size depends entirely on your users' questions.

A diagram shows a graph with a sharp downward dip in recall.

1 reads

Oct 07, 2025

rag11 min read

Why Your RAG Pilot Won't Survive Production

A RAG pilot on 200 curated documents looks magical, but scaling to 200,000 uncurated ones in production causes it to break. This article explains why recall collapses, how to fix a failing RAG pipeline, and what you should be measuring instead.

A graph shows recall dropping sharply as document count increases.

2 reads