<?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 Bogdan Novosad — Staff Software Engineer, AI Developer Tools</title><link>https://sacrorum.com/tags/llm/</link><description>Recent content in Llm on Bogdan Novosad — Staff Software Engineer, AI Developer Tools</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright 2024 Bogdan Novosad</copyright><lastBuildDate>Wed, 18 Feb 2026 18:45:12 +0100</lastBuildDate><atom:link href="https://sacrorum.com/tags/llm/index.xml" rel="self" type="application/rss+xml"/><item><title>Better than LSP for LLM coding agents</title><link>https://sacrorum.com/posts/better-than-lsp-for-llms/</link><pubDate>Wed, 18 Feb 2026 09:00:00 +0100</pubDate><guid>https://sacrorum.com/posts/better-than-lsp-for-llms/</guid><description>LSP was built to power IDE UX. Glider MCP is built to power LLM workflows—fewer calls, fewer tokens, less state pain, and better results on large C#/.NET codebases.</description></item><item><title>It’s genuinely satisfying when an LLM finds your MCP server helpful (9/10)</title><link>https://sacrorum.com/posts/glider-mcp-helpful-9-of-10/</link><pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate><guid>https://sacrorum.com/posts/glider-mcp-helpful-9-of-10/</guid><description>A practical comparison of LLM workflows in a large C# codebase: plain text search vs Roslyn-powered MCP tools (symbols, types, references, callers) — and why autosync changes the ergonomics.</description></item></channel></rss>