<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Proptest on Inanna Malick</title>
    <link>https://recursion.wtf/tags/proptest/</link>
    <description>Recent content in Proptest on Inanna Malick</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://recursion.wtf/tags/proptest/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Property Testing with Agent Swarms</title>
      <link>https://recursion.wtf/posts/agents-and-property-tests/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://recursion.wtf/posts/agents-and-property-tests/</guid>
      <description>&lt;p&gt;Have agents build the machinery to find bugs in your repo, then let that machinery generate and check cases without spending tokens on each one. You can do this with ordinary coding agents, without access to a closed cybersecurity program. Writing reference implementations, generators, and assertions for every custom data structure and algorithm is now work you can hand to a swarm.&lt;/p&gt;&#xA;&lt;p&gt;Pick a complex repo at work. Ask the people who know it well which parts worry them. Give a strong planning agent &lt;a href=&#34;https://gist.github.com/inanna-malick/4e042889df0d8737794a875dda7c8f3c&#34;&gt;these starter instructions&lt;/a&gt; and those leads. Target custom data structures, query planners, graph algorithms: complicated behavior with a simple way to check correctness.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
