<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ousley.ai — Writing</title>
    <link>https://www.ousley.ai/writing/</link>
    <description>Notes on where AI coding agents break on real Apple work.</description>
    <language>en-us</language>
    <atom:link href="https://www.ousley.ai/writing/feed.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Mon, 29 Jun 2026 16:27:40 GMT</lastBuildDate>
    <item>
      <title>Watch a coding agent silence a Swift 6 data race instead of fixing it</title>
      <link>https://www.ousley.ai/writing/silencing-swift-6-data-races/</link>
      <guid isPermaLink="true">https://www.ousley.ai/writing/silencing-swift-6-data-races/</guid>
      <pubDate>Mon, 29 Jun 2026 16:27:40 GMT</pubDate>
      <description>Hand a coding agent a Swift 6 strict-concurrency error and it often makes the build green by silencing the check, leaving the data race in place.</description>
    </item>
    <item>
      <title>Coding agents are good at writing Swift. They're bad at finishing it.</title>
      <link>https://www.ousley.ai/writing/agents-good-at-swift-bad-at-finishing/</link>
      <guid isPermaLink="true">https://www.ousley.ai/writing/agents-good-at-swift-bad-at-finishing/</guid>
      <pubDate>Mon, 22 Jun 2026 16:52:48 GMT</pubDate>
      <description>Frontier models write good Swift. Where coding agents come apart is finishing the work: intent mismatches, races that compile, and fixes that loop.</description>
    </item>
  </channel>
</rss>
