<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Internal-Systems on Cotomy Design Notes</title>
    <link>https://blog.cotomy.net/tags/internal-systems/</link>
    <description>Recent content in Internal-Systems on Cotomy Design Notes</description>
    <image>
      <title>Cotomy Design Notes</title>
      <url>https://blog.cotomy.net/img/ogp.jpg</url>
      <link>https://blog.cotomy.net/img/ogp.jpg</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <copyright>2026 Y. Arakawa</copyright>
    <lastBuildDate>Sun, 07 Jun 2026 12:54:00 +0000</lastBuildDate>
    <atom:link href="https://blog.cotomy.net/tags/internal-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why I Avoided a SPA for a Large Internal System</title>
      <link>https://blog.cotomy.net/posts/misc/why-most-internal-systems-do-not-need-a-spa/</link>
      <pubDate>Sun, 07 Jun 2026 12:54:00 +0000</pubDate>
      <guid>https://blog.cotomy.net/posts/misc/why-most-internal-systems-do-not-need-a-spa/</guid>
      <description>A field note from building a large internal business system, explaining why I considered a SPA, why I abandoned that approach, and why small server-rendered screens with selective AJAX fit the work better.</description>
    </item>
  </channel>
</rss>
