<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SDD on Tai&#39;s Life</title>
    <link>https://taislife.work/tags/sdd/</link>
    <description>Recent content in SDD on Tai&#39;s Life</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 31 Jan 2026 22:42:38 +0800</lastBuildDate>
    <atom:link href="https://taislife.work/tags/sdd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[Deep Dive] What is SDD?</title>
      <link>https://taislife.work/blogs/what-is-sdd/</link>
      <pubDate>Sat, 31 Jan 2026 22:42:38 +0800</pubDate>
      <guid>https://taislife.work/blogs/what-is-sdd/</guid>
      <description>&lt;p&gt;The term &lt;code&gt;SDD (Spec Driven Development)&lt;/code&gt; has been popping up everywhere this past year, and in Taiwan, it has become incredibly &amp;ldquo;hot&amp;rdquo; over the last six months.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://taislife.work/images/blogs/what-is-sdd/google-trend.png&#34; alt=&#34;google-trend&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;In a recent side project, while I was researching fully automated AI coding workflows, I decided to take a serious look at the core philosophy behind this buzzword.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-traditional-software-development-workflow&#34;&gt;The Traditional Software Development Workflow&lt;/h2&gt;&#xA;&lt;p&gt;As the old dev proverb goes: &lt;code&gt;“If it works, don’t touch it.”&lt;/code&gt; Since traditional development processes have birthed some of the world&amp;rsquo;s greatest works, there must be a solid logic behind them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
