<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Srinath Therampattil</title><description>Srinath Therampattil — Staff Engineer at Airbnb with 15 years building enterprise platforms. Writing on agentic AI, Salesforce platform engineering, and making AI reliable on systems of record.</description><link>https://srinaththerampattil.com/</link><item><title>Two Coding Agents, One Project Brief</title><link>https://srinaththerampattil.com/blog/two-agents-one-brief/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/two-agents-one-brief/</guid><description>I run Claude Code and Codex over the same repo, and each wants its own instructions file. Maintaining two by hand means they drift, and a stale project brief is worse than none. The fix is boring, and it&apos;s a symlink.</description><pubDate>Tue, 16 Jun 2026 09:30:00 GMT</pubDate></item><item><title>How the Creator of Claude Code Actually Uses It</title><link>https://srinaththerampattil.com/blog/how-claude-codes-creator-uses-it/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/how-claude-codes-creator-uses-it/</guid><description>Boris Cherny built Claude Code, and the way he uses it isn&apos;t about clever settings. It&apos;s about running it like a small team instead of a chat window. The handful of habits behind that, and the ones I&apos;ve adopted.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Your AI Tools Start From Zero Every Time. They Don&apos;t Have To.</title><link>https://srinaththerampattil.com/blog/ai-tools-that-compound/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/ai-tools-that-compound/</guid><description>AI coding tools forget everything between sessions, so they repeat mistakes and relearn your conventions over and over. Here&apos;s the learnings loop that fixes it, and exactly how I wired it into Claude Code on this blog.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Putting AI in Front of a Platform: Lessons from Real Systems</title><link>https://srinaththerampattil.com/blog/putting-ai-in-front-of-a-platform/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/putting-ai-in-front-of-a-platform/</guid><description>What I&apos;ve learned putting LLMs and agents on top of a Salesforce platform, where the data has rules you don&apos;t get to ignore and a wrong answer lands in the system the business runs on.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Designing Reliable AI Agents on Top of Enterprise Platforms</title><link>https://srinaththerampattil.com/blog/reliable-ai-agents-on-enterprise-platforms/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/reliable-ai-agents-on-enterprise-platforms/</guid><description>An agent that can change records on a system of record is powerful and risky in equal measure. The guardrails I rely on — acting as the user, idempotent actions, a narrow toolset, human checkpoints, and real logging — to let one run safely.</description><pubDate>Sat, 13 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Building Reliable LLM Features: What Production Actually Demands</title><link>https://srinaththerampattil.com/blog/building-reliable-llm-features/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/building-reliable-llm-features/</guid><description>An LLM feature is easy to demo and hard to trust. These are the practical habits — validating output, measuring quality, versioning prompts, and planning for wrong answers — that I rely on to make one hold up with real users.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Non-Functional Requirements for AI Systems: What Staff Engineers Should Specify</title><link>https://srinaththerampattil.com/blog/nfrs-for-ai-systems/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/nfrs-for-ai-systems/</guid><description>Most teams spec what an AI feature should do and skip how well it has to do it. The non-functional requirements — accuracy, latency, cost, fallback, observability, governance — that decide whether it&apos;s actually production-ready.</description><pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate></item><item><title>How I Evaluate LLM Output Without a Ground-Truth Dataset</title><link>https://srinaththerampattil.com/blog/evaluating-llm-output-without-ground-truth/</link><guid isPermaLink="true">https://srinaththerampattil.com/blog/evaluating-llm-output-without-ground-truth/</guid><description>You almost never have labeled data when you ship an AI feature. A practical way to measure quality anyway — a small hand-built set, plain assertions, a checked model-as-judge, and the production signals you already have.</description><pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate></item></channel></rss>