<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="https://purl.org/dc/elements/1.1/"
    xmlns:sy="https://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="https://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="https://purl.org/rss/1.0/modules/content/">

    <channel>

    <title><![CDATA[Writing]]></title>
    <link>http://eric.mithra62.com/index.php</link>
    <description></description>
    <dc:language>en</dc:language>
    <dc:creator>eric@mithra62.com</dc:creator>
    <dc:rights>Copyright 2026</dc:rights>
    <dc:date>2026-08-06T15:00:00+00:00</dc:date>
    <admin:generatorAgent rdf:resource="https://expressionengine.com/" />


    <item>
      <title><![CDATA[Alpha is Permission to Be Wrong]]></title>
      <link>https://mithra62.com/writing/alpha-is-permission-to-be-wrong</link>
      <guid>https://mithra62.com/writing/alpha-is-permission-to-be-wrong#When:15:00:00Z</guid>
      <description><![CDATA[<p>Alpha software is supposed to break. APIs change, schemas move, and sometimes the right upgrade path really is starting over. As I get AdAstra ready for its first developers, I'm learning that instability isn't the problem. Carelessness is.</p>
{body}]]></description>
      <dc:subject><![CDATA[Brain Dump, Programming, AdAstra]]></dc:subject>
      <dc:date>2026-08-06T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Done Happens Offstage]]></title>
      <link>https://mithra62.com/writing/done-happens-offstage</link>
      <guid>https://mithra62.com/writing/done-happens-offstage#When:15:00:00Z</guid>
      <description><![CDATA[<p>Tests pass. The package resolves. The docs exist. That's complete. &quot;Done&quot; is harder. Two open-source projects I once considered failures eventually became useful in ways I never planned, and taught me that releasing software means giving up some control over what it becomes.</p>
{body}]]></description>
      <dc:subject><![CDATA[Programming, Tech, Rant, AdAstra]]></dc:subject>
      <dc:date>2026-08-05T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Confidence Doesn&#8217;t Need an Audience]]></title>
      <link>https://mithra62.com/writing/confidence-doesnt-need-an-audience</link>
      <guid>https://mithra62.com/writing/confidence-doesnt-need-an-audience#When:15:00:00Z</guid>
      <description><![CDATA[<p>Being underestimated professionally never bothered me as much as being misunderstood personally.</p>
{body}]]></description>
      <dc:subject><![CDATA[Business, Brain Dump, Rant]]></dc:subject>
      <dc:date>2026-07-29T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[The Greatest Hits of ExpressionEngine History]]></title>
      <link>https://mithra62.com/writing/the-greatest-hits-of-expressionengine-history</link>
      <guid>https://mithra62.com/writing/the-greatest-hits-of-expressionengine-history#When:15:00:00Z</guid>
      <description><![CDATA[<p>ExpressionEngine's history isn't just software. It's licensing drama, conference stories, community legends, and a platform that somehow survived all of it.</p>
{body}]]></description>
      <dc:subject><![CDATA[Brain Dump, Business, Rant, ExpressionEngine]]></dc:subject>
      <dc:date>2026-07-22T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Introducing AdAstra (The Software Got Here First)]]></title>
      <link>https://mithra62.com/writing/introducing-adastra-the-software-got-here-first</link>
      <guid>https://mithra62.com/writing/introducing-adastra-the-software-got-here-first#When:15:00:00Z</guid>
      <description><![CDATA[<p>Introducing AdAstra: a content platform where your content model comes first and the software shipped before the announcement did. Two alphas in, with the roadmap, the known issues, and the money talk all on the table.</p>
{body}]]></description>
      <dc:subject><![CDATA[Business, Programming, Tech, Code]]></dc:subject>
      <dc:date>2026-07-21T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Phase 9: The New Platform]]></title>
      <link>https://mithra62.com/writing/phase-9-the-new-platform</link>
      <guid>https://mithra62.com/writing/phase-9-the-new-platform#When:15:00:00Z</guid>
      <description><![CDATA[<p>The migration is finished. The architecture is clean. Morale has returned. The platform finally feels manageable again. This is the phase where organizations discover that complexity wasn't the enemy. It was always part of the journey.</p>
{body}]]></description>
      <dc:subject><![CDATA[Business, Brain Dump, Tech, Programming]]></dc:subject>
      <dc:date>2026-07-15T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Phase 8: The Rewrite]]></title>
      <link>https://mithra62.com/writing/phase-8-the-rewrite</link>
      <guid>https://mithra62.com/writing/phase-8-the-rewrite#When:15:00:00Z</guid>
      <description><![CDATA[<p>Rewriting software sounds fun right up until you remember the old platform still has customers. This is the phase where optimism collides with reality, hidden business rules emerge from the shadows, and teams discover that the hardest part of a rewrite isn't writing code. It's understanding what the old code was actually doing.</p>
{body}]]></description>
      <dc:subject><![CDATA[Business, Brain Dump, Programming, Rant]]></dc:subject>
      <dc:date>2026-07-08T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Phase 7: The Rebuild Conversation]]></title>
      <link>https://mithra62.com/writing/phase-7-the-rebuild-conversation</link>
      <guid>https://mithra62.com/writing/phase-7-the-rebuild-conversation#When:15:09:00Z</guid>
      <description><![CDATA[<p>There are few meetings in software engineering more dangerous than the first serious rewrite discussion. Not because rewrites are inherently bad, but because the conversation is rarely about code. It's about trust, frustration, risk, and whether the organization understands the problem it's trying to solve.</p>
{body}]]></description>
      <dc:subject><![CDATA[Brain Dump, Tech, Programming, Rant]]></dc:subject>
      <dc:date>2026-07-01T15:09:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Phase 6: Stabilization Attempts]]></title>
      <link>https://mithra62.com/writing/phase-6-stabilization-attempts</link>
      <guid>https://mithra62.com/writing/phase-6-stabilization-attempts#When:15:00:00Z</guid>
      <description><![CDATA[<p>The platform is struggling. The team is exhausted. The roadmap is slipping. Naturally, someone suggests a framework migration. This is the phase where organizations start searching for stability and discover that complexity is much easier to move than eliminate.</p>
{body}]]></description>
      <dc:subject><![CDATA[Brain Dump, Programming, Tech, Rant]]></dc:subject>
      <dc:date>2026-06-24T15:00:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Phase 5: Architecture Strain]]></title>
      <link>https://mithra62.com/writing/phase-5-architecture-strain</link>
      <guid>https://mithra62.com/writing/phase-5-architecture-strain#When:15:00:00Z</guid>
      <description><![CDATA[<p>The platform isn't broken. It's resisting change. This is the phase where complexity becomes operational, process expands to compensate for instability, and organizations discover that the real bottleneck isn't capacity. It's understanding.</p>
{body}]]></description>
      <dc:subject><![CDATA[Programming, Tech, Rant, Code]]></dc:subject>
      <dc:date>2026-06-17T15:00:00+00:00</dc:date>
    </item>


    </channel>
</rss>