Building AI With AI on Claude Code
How I use Claude Code's agent system to build AI systems — with a mandatory Advisor that catches production bugs, persistent memory that compounds across sessions, and a full EKS deployment architecture.
Read →
Field Notes RSS
Production notes from the intersection of drug discovery, cloud infrastructure, and autonomous AI — what actually ships.
I build the platforms that let scientists focus on curing disease instead of fighting infrastructure. 12 years in enterprise cloud, specializing in Agentic AI and production-grade platform engineering for pharmaceutical R&D on AWS — embedding AI agents and LLM-assisted workflows into drug discovery pipelines.
My edge: I don't just build platforms. I make them disappear so the science can move faster.
Featured
Try a different search term or clear your filters.
How I use Claude Code's agent system to build AI systems — with a mandatory Advisor that catches production bugs, persistent memory that compounds across sessions, and a full EKS deployment architecture.
Read →How I built a 35-tool AI agent that autonomously queries databases, builds knowledge graphs, and generates research reports — running on Kubernetes.
Read →Why one agent isn't enough — and how to build a team of AI specialists that research, analyze, synthesize, and critique each other's work, with full observability via Langfuse.
Read →Your invoice tells you the total. It never tells you who spent it, which tokens were wasted, or whether the last model upgrade paid for itself.
Read →Building a standing internal evaluation suite — and the four ways my harness broke before it produced a single trustworthy number.
Read →Security lessons from putting an autonomous, tool-calling agent in front of regulated enterprise data — including a cross-tenant vulnerability I shipped, found, and closed.
Read →I run agents on Kubernetes and evaluated moving them to a managed agent platform. Here's what genuinely improves, what quietly becomes your problem, and why a hybrid split was the honest answer.
Read →The agent gets the credit. The data pipeline does the work. Here's the production ingestion architecture that keeps a 19-source research agent reliable.
Read →A tag-only image bump left the UI, presentation, and diagrams five versions stale. None of it errored. Here's what a real AI system release checklist looks like.
Read →Not fine-tuning. Not prompt-stuffing. A skills system that retrieves domain heuristics at query time — and the failure modes that shaped it.
Read →Langfuse catches bad tool data. Prometheus catches the stuck pod. CloudWatch catches the $12 session. Here's how three layers work together — and where each one falls short alone.
Read →Every session starts cold. Users re-teach the same preferences. Here's how to give your agent real memory without creating a privacy disaster.
Read →The agent was wrong. The user corrected it. The next user got the same wrong answer. Here's how to close the loop — without fine-tuning.
Read →We had a design. The advisor caught five blockers before a single line was written. Here's what changed and why it mattered.
Read →Burst GPU workloads, silent Karpenter version traps, and why a draining SQS consumer will break your ScaledJob scaling.
Read →We built the join, ran it, got 1.8% coverage. It looked like a data problem. It was a .lower() call — and two more silent bugs followed.
Read →The migration looked straightforward. Then we found five categories of blockers. Here's the framework we wish we'd had before we started.
Read →The console can't see the bucket. The role goes in the destination account. KMS is always the first thing that breaks. Here's the complete playbook.
Read →Hop 1: EKS pod gets IRSA credentials. Hop 2: assumes a role in a different account. Here's how to wire both hops without creating a credential management nightmare.
Read →One source for the chart in your registry. One source for the values in Git. They version independently — and that changes everything about how you manage environments.
Read →You query CloudWatch. You get zero results. No error. The logs are there — in a different region. Here's how to build multi-account extraction that doesn't silently fail.
Read →AI systems are only as good as the data pipelines that feed them. Here's how to build infrastructure that produces genuinely AI-ready data — and the silent failures that break it before training starts.
Read →Your agent answered a question. Was it correct? How long did it take? What did it cost? Did it use the right prompt version? Langfuse answers all of those — and makes the answers actionable.
Read →