<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Backend on Clarence | Backend, AI, DevOps, Infrastructure</title>
    <link>https://clarence.tw/en/tags/backend/</link>
    <description>Recent content in Backend on Clarence | Backend, AI, DevOps, Infrastructure</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 08 Jul 2026 00:30:00 +0800</lastBuildDate><atom:link href="https://clarence.tw/en/tags/backend/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Work: Backend, AI, DevOps, and Infrastructure</title>
      <link>https://clarence.tw/en/posts/technical-delivery-chain/</link>
      <pubDate>Wed, 08 Jul 2026 00:30:00 +0800</pubDate>
      
      <guid>https://clarence.tw/en/posts/technical-delivery-chain/</guid>
      <description>&lt;p&gt;I do not treat Backend, AI, DevOps, Infrastructure, and Network as isolated areas. For a product that has to go online, be used, and remain maintainable, these layers eventually become one delivery chain.&lt;/p&gt;
&lt;p&gt;Features need stable APIs. Services need reliable CI/CD. Long-running systems need monitoring, backup, network visibility, and security. When a product needs LLMs, Speech AI, or GPU runtime, model integration also has to be deployable, observable, and operable.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
