Redoing a website is hard work, even in the age of AI. It took me a whole day. Now using Astro v5 and a new theme.
Peppa Pig: “Will you finish it today?”
Mr. Bull: “Oh, no! You can’t build a house in a day. It’ll be finished… tomorrow.”
Welcome to the garden of Anurag Bhandari the developer. I am a generalist software engineer.
This little space on the web is where I write about my coding adventures, mishappenings, and breif notes in the hopes that my future self (or you) will find something useful.
🎩 Hats I have worn: Linux dev, system troubleshooter, .NET developer, full-stack engineer, applied R&D technologist, front-end architect, API wiz, and (more recently) engineering manager.
At heart, I am an excitable developer with a penchant for ✨ shiny new things, 🧪 experiments, 🪴 growth, and 🙂 emojis.
Find me on
The deep dive into how a request travels across the MCP stack and how a response is transported back is the best damn example I’ve ever read about how MCPs work.
The correlation (or the lack of) between speed/latency and efficiency in the conclusion is confusing. Ideally, more efficient systems should offer better speeds with similar resources. Is the mentioned efficiency expressed purely in terms of scalability? Can someone enlighten me?
Great historical context about a key problem RAG was designed to solve and why there is a better solution now in agentic search - thanks to huge context windows in today’s LLMs. It’s also fascinating to learn how Claude Code cleverly uses decades-old filesystem tools to perform lightning fast navigation and regex searches without needing some sort of indexing.