<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Concurrency on Tyler Stapler&#39;s Personal Website</title>
    <link>/tags/concurrency/</link>
    <description>Recent content in Concurrency on Tyler Stapler&#39;s Personal Website</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Copyright &amp;#169; by Tyler Stapler</copyright>
    <lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/concurrency/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Structured Concurrency is a Footgun for Mixed-Experience Teams</title>
      <link>/blog/structured-concurrency-footgun/</link>
      <pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/blog/structured-concurrency-footgun/</guid>
      <description>The concurrency model you choose is an implicit contract with your entire team. Kotlin coroutines are brilliant engineering — but they make a promise the JVM&amp;rsquo;s type system cannot enforce, and the failure modes are silent, gradual, and catastrophic. Here&amp;rsquo;s why we deprecated Reactor the week virtual threads hit GA, and what we&amp;rsquo;d tell ourselves before we started.</description>
    </item>
  </channel>
</rss>
