<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>theChris.in — Systems, Failure, Longevity</title><link>https://thechris.in/</link><description>Essays on systems, failure modes, and building software that lasts.</description><generator>Hugo</generator><language>en-US</language><managingEditor>hello@thechris.in (Chris Roy)</managingEditor><webMaster>hello@thechris.in (Chris Roy)</webMaster><copyright>© 2025 theChris.in. Read freely. Attribute generously. #obviously</copyright><lastBuildDate>Thu, 09 Apr 2026 13:50:12 +0530</lastBuildDate><atom:link href="https://thechris.in/index.xml" rel="self" type="application/rss+xml"/><item><title>Greenfield and the cost of amnesia</title><link>https://thechris.in/articles/greenfield-and-the-cost-of-amnesia/</link><pubDate>Thu, 09 Apr 2026 13:50:12 +0530</pubDate><author>hello@thechris.in (Chris Roy)</author><guid isPermaLink="true">https://thechris.in/articles/greenfield-and-the-cost-of-amnesia/</guid><description> Every system eventually invites a rewrite.&amp;#xA;Not because it fails. But because it becomes difficult to change.&amp;#xA;The structure feels rigid. The decisions feel outdated. The system resists modification in ways that are hard to explain and harder to justify.&amp;#xA;A clean slate appears …</description><category>Architecture</category></item><item><title>Why most plugin systems fail quietly</title><link>https://thechris.in/articles/why-most-plugin-systems-fail-quietly/</link><pubDate>Wed, 31 Dec 2025 15:30:17 +0530</pubDate><author>hello@thechris.in (Chris Roy)</author><guid isPermaLink="true">https://thechris.in/articles/why-most-plugin-systems-fail-quietly/</guid><description>Most plugin systems continue to work, but just well enough.&amp;#xA;This is what makes them dangerous.&amp;#xA;A typical plugin system begins with a reasonable goal: allow extension without modification. The core remains stable. Optional functionality lives at the edges. Responsibility is …</description><category>Architecture</category></item><item><title>On building software that deserves to last</title><link>https://thechris.in/articles/on-building-software-that-deserves-to-last/</link><pubDate>Wed, 31 Dec 2025 12:54:52 +0530</pubDate><author>hello@thechris.in (Chris Roy)</author><guid isPermaLink="true">https://thechris.in/articles/on-building-software-that-deserves-to-last/</guid><description> Correctness is a low bar.&amp;#xA;Most systems that reach production clear it. They compile. They pass tests. They satisfy the requirements as they were understood at the time. And yet, many of these systems become difficult to touch within a few years. Not because the problem was …</description><category>Foundational</category></item><item><title>On restraint, boundaries, and systems thinking</title><link>https://thechris.in/articles/on-restraint-boundaries-and-systems-thinking/</link><pubDate>Tue, 30 Dec 2025 23:30:56 +0530</pubDate><author>hello@thechris.in (Chris Roy)</author><guid isPermaLink="true">https://thechris.in/articles/on-restraint-boundaries-and-systems-thinking/</guid><description>Most systems do not fail because they were poorly designed. They fail because they violate constraints that were never made explicit.&amp;#xA;At the beginning, most systems are tractable. The architecture is coherent. The abstractions are limited. The number of active invariants is small …</description><category>Foundational</category></item></channel></rss>