<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: The Scratchy Cat</title>
    <description>The latest articles on DEV Community by The Scratchy Cat (@the_scratchy_cat).</description>
    <link>https://dev.to/the_scratchy_cat</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3690321%2F1f05b97c-6731-4fed-b1ba-6eefd99e6adc.jpg</url>
      <title>DEV Community: The Scratchy Cat</title>
      <link>https://dev.to/the_scratchy_cat</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/the_scratchy_cat"/>
    <language>en</language>
    <item>
      <title>Why Centralized AI Became the Default — and Why That Assumption May No Longer Hold</title>
      <dc:creator>The Scratchy Cat</dc:creator>
      <pubDate>Fri, 02 Jan 2026 18:28:25 +0000</pubDate>
      <link>https://dev.to/the_scratchy_cat/why-centralized-ai-became-the-default-and-why-that-assumption-may-no-longer-hold-2c33</link>
      <guid>https://dev.to/the_scratchy_cat/why-centralized-ai-became-the-default-and-why-that-assumption-may-no-longer-hold-2c33</guid>
      <description>&lt;p&gt;Over the last decade, we’ve mostly talked about AI in terms of scale: bigger models, more GPUs, larger data centers. Centralization slowly became the default assumption, often without being explicitly questioned.&lt;/p&gt;

&lt;p&gt;This piece is an attempt to step back and look at the system as a whole — not from a hype perspective, but from an architectural one. Where do the real constraints come from? Which ones are still binding, and which ones are quietly dissolving as inference becomes dominant and hardware evolves?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbmbxks6omuq8b0apscdz.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbmbxks6omuq8b0apscdz.jpg" alt=" " width="800" height="446"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’m not arguing for a particular ideology or for the disappearance of centralized systems. I’m more interested in understanding what is actually becoming possible again, and what kinds of design choices we may soon have to make — whether we’re ready for them or not.&lt;/p&gt;

&lt;p&gt;If you work close to the metal — infra, ML systems, hardware, distributed systems — I’d be genuinely curious how this resonates with your experience.&lt;/p&gt;

&lt;p&gt;👉 Read the full piece here: &lt;a href="https://medium.com/@jan.olsen/if-ai-is-centralized-today-it-is-not-a-law-of-nature-f70bd431888b" rel="noopener noreferrer"&gt;If AI is centralized today, it is not a law of nature&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
