Gu-log Picks

Long-form articles, translated and explained

269 posts

← Back to home

9 AI Agents Working at Once: The Context Problem, Race Conditions, and ECC's Fix

After running nine Claude Code agents in parallel, we hit an article counter race and a git lock conflict. ECC's iterative retrieval pattern points at the same multi-agent problem: shared context needs isolated state, atomic pre-allocation, and sequential deploy.

Claude Code Burning Your Budget? One Setting Saves 60% on Tokens

Most token waste is invisible: Extended Thinking on tasks that don't need it, Opus handling work a Sonnet could do, context filling before you compact. ECC's token-optimization.md combines MAX_THINKING_TOKENS + model routing + strategic compact — author Affaan Mustafa says the savings reach 60-80%.

Eval-Driven Development — You Test Your Code, But Who Tests Your AI?

You use unit tests to check your code and CI to protect your pipeline. But who checks your AI? Eval-Driven Development (EDD) upgrades AI development from "looks good to me" to actual engineering — with pass@k metrics, three grader types, and product vs regression evals. This is TDD for the AI era.

Git Hooks Changed How You Write Code. AI Hooks Are Doing It Again.

Git hooks work even when you forget they exist. AI hooks make your Claude Code follow rules even when it forgets. ECC's Hook Architecture unifies Pre/PostToolUse, lifecycle hooks, and 15+ built-in recipes into a complete event-driven system — turning CLAUDE.md suggestions into actual enforcement.

You Don't Have to Watch Claude Code — ECC's Six Autonomous Loop Patterns

Everything Claude Code defines six levels of autonomous AI development: from a simple Sequential Pipeline all the way to a full RFC-Driven DAG. Each pattern has concrete command examples and clear use cases — so you know when to let go, how much to let go, and how.

Bash Is All You Need? Why Even Non-Coding Agents Need a Shell

Anthropic engineer Thariq argues that even non-coding agents need bash. Saving intermediate results to files lets an agent search, compose API workflows, retry, and verify its own work — but it also raises real questions about security, data exfiltration, and container-based deployment.

How LangChain Evals Deep Agents — More Evals ≠ Better Agents

LangChain shares how they built an eval system for Deep Agents: not by piling on more tests, but by using targeted evals that measure exactly what matters in production. From data sources to metrics design to actually running evals — the full methodology.