<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV BY SAL — Writing</title>
    <link>https://by-sal.dev</link>
    <description>DEV BY SAL is a small senior software studio that builds AI-native products, frontier infrastructure and revenue-shifting platforms for ambitious companies.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 05:07:53 GMT</lastBuildDate>
    <atom:link href="https://by-sal.dev/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>The AI product engineer is the new full-stack engineer</title>
      <link>https://by-sal.dev/insights/the-ai-product-engineer</link>
      <guid isPermaLink="true">https://by-sal.dev/insights/the-ai-product-engineer</guid>
      <pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Insights</category>
      <description>Senior product engineering used to mean comfort across the front-end, the back-end, and the database. The bar has moved. The teams shipping consequential software in 2026 demand a fourth competency — turning probabilistic models into reliable product behavior — and the engineers who have it are the highest-leverage hires on the org chart.</description>
    </item>
    <item>
      <title>The four-week MVP, defended</title>
      <link>https://by-sal.dev/blog/the-four-week-mvp</link>
      <guid isPermaLink="true">https://by-sal.dev/blog/the-four-week-mvp</guid>
      <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Blog</category>
      <description>People keep asking why we ship in four weeks instead of six months. It&apos;s not because we&apos;re faster. It&apos;s because four weeks is what&apos;s actually required to learn anything.</description>
    </item>
    <item>
      <title>Eval-driven development for production LLM systems</title>
      <link>https://by-sal.dev/papers/eval-driven-development-for-llm-systems</link>
      <guid isPermaLink="true">https://by-sal.dev/papers/eval-driven-development-for-llm-systems</guid>
      <pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Paper</category>
      <description>Most production LLM systems are evaluated by other LLMs, against benchmarks that have probably leaked into the model&apos;s training data, with judges that systematically prefer their own kin. The recent literature is clear-eyed about all three problems. This paper is a working playbook for shipping evaluation infrastructure that survives those facts.</description>
    </item>
    <item>
      <title>Agent architectures that actually ship</title>
      <link>https://by-sal.dev/papers/agent-architecture-patterns-2026</link>
      <guid isPermaLink="true">https://by-sal.dev/papers/agent-architecture-patterns-2026</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Paper</category>
      <description>The literature on production LLM agents has matured from &quot;can we make this work at all?&quot; to &quot;which interface and memory structure makes it work reliably?&quot; This paper walks the dominant patterns — ReAct, Reflexion, AutoGen-style multi-agent, and SWE-agent&apos;s interface-as-product — and the failure modes that come with them.</description>
    </item>
    <item>
      <title>The cost of the second pilot</title>
      <link>https://by-sal.dev/insights/the-cost-of-the-second-pilot</link>
      <guid isPermaLink="true">https://by-sal.dev/insights/the-cost-of-the-second-pilot</guid>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Insights</category>
      <description>AI pilots are easier to start than ever and harder to ship than they look. The teams that fail almost all fail in the same place — between the first design partner and the second customer, when the demo has to become a product. This is what that gap actually costs, and how to budget for it.</description>
    </item>
    <item>
      <title>Why we (mostly) don&apos;t use LLM frameworks</title>
      <link>https://by-sal.dev/blog/why-we-dont-use-llm-frameworks</link>
      <guid isPermaLink="true">https://by-sal.dev/blog/why-we-dont-use-llm-frameworks</guid>
      <pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Blog</category>
      <description>LangChain, LlamaIndex, Haystack — we have used them all and we ship most of our agents without them. Here is when frameworks help, when they hurt, and why we usually choose the harder-looking option.</description>
    </item>
    <item>
      <title>Why &quot;build vs. buy&quot; just flipped</title>
      <link>https://by-sal.dev/insights/why-build-versus-buy-just-flipped</link>
      <guid isPermaLink="true">https://by-sal.dev/insights/why-build-versus-buy-just-flipped</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Insights</category>
      <description>For two decades, &quot;buy the SaaS&quot; was the right answer for almost any internal-tool question. The economics that made that true are no longer true. We walk through what changed, what it means for vendor selection, and which categories are most exposed.</description>
    </item>
    <item>
      <title>The eval set is the spec</title>
      <link>https://by-sal.dev/blog/the-eval-set-is-the-spec</link>
      <guid isPermaLink="true">https://by-sal.dev/blog/the-eval-set-is-the-spec</guid>
      <pubDate>Sat, 18 Apr 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Blog</category>
      <description>For LLM-shaped products, the document that defines what the product does is the eval set, not the PRD. We have stopped writing PRDs for AI features and started writing the cases. The work is better for it.</description>
    </item>
    <item>
      <title>RAG that actually retrieves</title>
      <link>https://by-sal.dev/papers/rag-that-actually-retrieves</link>
      <guid isPermaLink="true">https://by-sal.dev/papers/rag-that-actually-retrieves</guid>
      <pubDate>Sun, 15 Mar 2026 00:00:00 GMT</pubDate>
      <dc:creator>Sal Anvarov</dc:creator>
      <category>Paper</category>
      <description>Production RAG in 2026 looks nothing like the &quot;embed, retrieve, generate&quot; of 2023. The recent literature converges on retrieval as a routing problem — when to retrieve, how to verify retrieval quality, when to switch to graph indexing, when to lean on long-context instead. This paper is the practitioner-facing version.</description>
    </item>
  </channel>
</rss>
