<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Singleton on Coyote Time</title><link>https://blog.jonmikeys.com/tags/singleton/</link><description>Recent content in Singleton on Coyote Time</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.jonmikeys.com/tags/singleton/index.xml" rel="self" type="application/rss+xml"/><item><title>Better Singletons in Unity: Ambient Services, Reset Hooks and Testable Globals</title><link>https://blog.jonmikeys.com/posts/better-singletons-in-unity/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.jonmikeys.com/posts/better-singletons-in-unity/</guid><description>A Unity singleton does two jobs at once: it limits a class to one instance and it makes that instance globally reachable. This post separates the two, covers the Unity-specific failure modes, and builds a small ambient service holder with an install step, a reset hook and a test override. The plain C# core was compiled and run.</description></item></channel></rss>