<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Llm on Girish Shekhar</title><link>https://blog.girishshekhar.com/tags/llm/</link><description>Recent content in Llm on Girish Shekhar</description><generator>Hugo -- 0.163.3</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.girishshekhar.com/tags/llm/index.xml" rel="self" type="application/rss+xml"/><item><title>The Harness Is the Agent</title><link>https://blog.girishshekhar.com/posts/harness-is-the-agents/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/harness-is-the-agents/</guid><description>For two years we have talked about building agents as if an agent were a thing you construct. It isn&amp;rsquo;t. The harness — the loop, the tools, the context discipline — is the artifact you actually build, version, and debug. This post reframes the agent as emergent behavior, explains why agent frameworks now feel wrong-shaped in production, and offers a way to decide when to own the loop and when to rent it.</description></item><item><title>Context Is the Real Engineering Problem</title><link>https://blog.girishshekhar.com/posts/agent-coordination-patterns/3-context-engineering-is-the-real-problem/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/agent-coordination-patterns/3-context-engineering-is-the-real-problem/</guid><description>The coordination patterns are well understood. The protocol layer is converging. The unsolved problem is context: how do you decide what to pass between agents, when to summarize versus delegate in full, and how to do this without the routing decision itself becoming the expensive part. This post lands the thesis — and examines what happens when agents coordinate asynchronously across disconnected environments.</description></item><item><title>Feedback Loops, Discovery, and Fault Tolerance</title><link>https://blog.girishshekhar.com/posts/agent-coordination-patterns/2-feedback-discovery-fault-tolerance/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/agent-coordination-patterns/2-feedback-discovery-fault-tolerance/</guid><description>The synchronous coordination patterns tell you how to decompose work. This post covers what happens when that work goes wrong — or when agents don&amp;rsquo;t yet know who can help. Iterative refinement, progressive discovery, fallback, and speculative execution are the patterns that govern self-correction, capability negotiation, and graceful degradation in production agent systems.</description></item><item><title>The Distributed Systems Playbook in a New Medium</title><link>https://blog.girishshekhar.com/posts/agent-coordination-patterns/1-synchornous-patterns/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/agent-coordination-patterns/1-synchornous-patterns/</guid><description>Multi-agent systems are not a new class of engineering problem. They are distributed systems with a different payload. This post maps the synchronous coordination patterns emerging in agent ecosystems — delegation, handoff, scatter-gather, chaining — to the primitives distributed systems engineers have used for decades, and explains why the medium changes the failure modes in ways that matter.</description></item><item><title>LLMs in Day-to-Day Engineering Work</title><link>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/7-real-world-application/</link><pubDate>Wed, 17 May 2023 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/7-real-world-application/</guid><description>After all the theory and architecture, this post looks at how experienced engineers actually use Large Language Models in their daily work — where they help, where they hurt, and how to integrate them without outsourcing thinking.</description></item><item><title>The Skills Engineers Need to Level Up for LLM-Based Systems</title><link>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/6-leveling-up/</link><pubDate>Wed, 03 May 2023 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/6-leveling-up/</guid><description>Large Language Models don’t just introduce new tools — they demand new skills. This post explains what actually changes for engineers and technical leaders when LLMs become part of production systems, and where traditional instincts need to be updated.</description></item><item><title>Retrieval-Augmented Generation (RAG): Grounding LLMs in Reality</title><link>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/5-retrieval-augmented-generation/</link><pubDate>Wed, 19 Apr 2023 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/5-retrieval-augmented-generation/</guid><description>Retrieval-Augmented Generation (RAG) is one of the most important architectural patterns to emerge alongside Large Language Models. This post explains why RAG exists, how it works, and what problems it actually solves — without turning it into a tooling tutorial.</description></item><item><title>Why LLMs Fail in Surprising Ways (And Why That’s Expected)</title><link>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/4-why-llms-fail/</link><pubDate>Wed, 05 Apr 2023 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/4-why-llms-fail/</guid><description>Large Language Models often fail in ways that feel inconsistent or irrational. This post explains why those failures are not bugs, but natural consequences of probabilistic systems trained on language — and what that means for real product and system design.</description></item><item><title>The LLM Landscape: Models, Capabilities, and Tradeoffs</title><link>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/3-the-llm-landscape/</link><pubDate>Wed, 29 Mar 2023 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/3-the-llm-landscape/</guid><description>Once you understand how LLMs work, the next real question is model choice. This post explains how to reason about LLM tradeoffs — capability, cost, controllability, and domain fit — without relying on benchmarks alone.</description></item><item><title>How LLMs Work (Only What You Need to Know)</title><link>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/2-how-llms-work/</link><pubDate>Wed, 22 Mar 2023 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/2-how-llms-work/</guid><description>A deeper look at how Large Language Models actually work — focusing on tokens, transformers, and training stages — explained in a way that helps engineers, product managers, and technical leaders reason about behavior and tradeoffs.</description></item><item><title>Why Large Language Models Changed the Game</title><link>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/1-why-llms-changed-the-game/</link><pubDate>Tue, 07 Mar 2023 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/llms-and-how-our-work-is-changing/1-why-llms-changed-the-game/</guid><description>Large Language Models feel different from earlier machine learning systems. This post explains why — focusing on tokens, training data, self-supervision, and the architectural patterns that changed how we build software.</description></item></channel></rss>