<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rust on Yesterday I was wrong</title>
    <link>/tags/rust/</link>
    <description>Recent content in Rust on Yesterday I was wrong</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 30 Apr 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Picking a Language for Agents</title>
      <link>/2026/04/30/picking-a-language-for-agents/</link>
      <pubDate>Thu, 30 Apr 2026 09:00:00 +0000</pubDate>
      <guid>/2026/04/30/picking-a-language-for-agents/</guid>
      <description>&lt;p&gt;This is the final part of a 5-part series on agentic engineering. &lt;a href=&#34;/2026/04/29/agentic-architecture/&#34;&gt;Part 4&lt;/a&gt; laid out architectural principles for choosing languages and runtimes. This post puts a handful of worked examples through those principles, just to show what the analysis looks like in practice.&lt;/p&gt;&#xA;&lt;p&gt;This isn&amp;rsquo;t a list of &amp;ldquo;the languages I use&amp;rdquo;, and it isn&amp;rsquo;t exhaustive. It&amp;rsquo;s a deliberate move &lt;em&gt;away&lt;/em&gt; from personal taste — what I happen to know, what&amp;rsquo;s fashionable, what the team is already comfortable with — and toward something more objective: which language properties best fit &lt;strong&gt;the agent&lt;/strong&gt; &lt;em&gt;and&lt;/em&gt; &lt;strong&gt;the problem domain&lt;/strong&gt; in front of you. Different problems will pull you toward different answers, and the examples below are picked specifically to make that point.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
