<?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 Community: Reese Cooper</title>
    <description>The latest articles on DEV Community by Reese Cooper (@reese_hacks).</description>
    <link>https://dev.to/reese_hacks</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4214128%2F58a96329-d5fc-4d1c-86ef-4439fc0c6b33.jpg</url>
      <title>DEV Community: Reese Cooper</title>
      <link>https://dev.to/reese_hacks</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/reese_hacks"/>
    <language>en</language>
    <item>
      <title>One feature in Flutter, Swift, and Kotlin: three small regrets</title>
      <dc:creator>Reese Cooper</dc:creator>
      <pubDate>Sun, 01 Nov 2026 15:10:12 +0000</pubDate>
      <link>https://dev.to/reese_hacks/one-feature-in-flutter-swift-and-kotlin-three-small-regrets-2e30</link>
      <guid>https://dev.to/reese_hacks/one-feature-in-flutter-swift-and-kotlin-three-small-regrets-2e30</guid>
      <description>&lt;p&gt;I built the same feature — a list with offline cache and pull to refresh — in three frameworks. The codebases were different but the regrets were identical.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Flutter:&lt;/strong&gt; the UI was the easy part. The mental shift was accepting that a widget rebuild is cheap only if you make it cheap. I had to learn to keep state out of the tree.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Swift:&lt;/strong&gt; everything reads beautifully until you hit SwiftUI's navigation state, and suddenly the clean code is a stack of enums and paths. Also, iOS reviewers will find the one screen you didn't test.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Kotlin:&lt;/strong&gt; coroutines made the async part pleasant, and then the lifecycle bit me. A scope tied to the wrong owner leaks in ways that are hard to reproduce.&lt;/p&gt;

&lt;p&gt;The shared lesson: the list is never the feature. The cache invalidation and the empty state are the feature, and every platform makes those boring in a different way.&lt;/p&gt;

&lt;p&gt;Which one would you pick next time?&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>swift</category>
      <category>kotlin</category>
      <category>mobile</category>
    </item>
    <item>
      <title>One small win from caching responses</title>
      <dc:creator>Reese Cooper</dc:creator>
      <pubDate>Thu, 29 Oct 2026 02:23:22 +0000</pubDate>
      <link>https://dev.to/reese_hacks/one-small-win-from-caching-responses-22jj</link>
      <guid>https://dev.to/reese_hacks/one-small-win-from-caching-responses-22jj</guid>
      <description>&lt;p&gt;Added a five-second cache to one expensive endpoint; median latency dropped by more than half. Not a deep insight: it was slow, we cached it, it got faster.&lt;/p&gt;

&lt;p&gt;The interesting part was the failure mode. Stale data looked fine in tests and confused everyone in production once an hour. We now return the cache age in a header, which costs nothing and saved a lot of confused debugging.&lt;/p&gt;

</description>
      <category>backend</category>
      <category>performance</category>
      <category>caching</category>
    </item>
  </channel>
</rss>
