<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Api-Design on Coyote Time</title>
    <link>https://blog.jonmikeys.com/tags/api-design/</link>
    <description>Recent content in Api-Design on Coyote Time</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.jonmikeys.com/tags/api-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Extension Methods in Unity: Make Calls Clear, Not Clever</title>
      <link>https://blog.jonmikeys.com/posts/extension-methods-in-unity/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/extension-methods-in-unity/</guid>
      <description>Use extension methods as small, honest vocabulary for Unity code while avoiding invisible cost, ambiguous APIs, fake-null traps, and miscellaneous helper drawers.</description>
    </item>
    <item>
      <title>Factory and Abstract Factory Patterns: Create the Thing Without Spreading the Choice Everywhere</title>
      <link>https://blog.jonmikeys.com/posts/factory-and-abstract-factory-patterns/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/factory-and-abstract-factory-patterns/</guid>
      <description>A practical guide to factory and abstract factory patterns in game code: when construction choices deserve a home, when a simple method is enough, and how to avoid turning creation code into architecture theater.</description>
    </item>
    <item>
      <title>Builder and Fluent Builder Patterns: Make Setup Readable Without Hiding the Cost</title>
      <link>https://blog.jonmikeys.com/posts/builder-fluent-builder-patterns/</link>
      <pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/builder-fluent-builder-patterns/</guid>
      <description>A practical guide to builder-style APIs in game code: when they clarify setup, when object initializers are enough, and where fluent chains become a trap.</description>
    </item>
  </channel>
</rss>
