<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software Design on ᕕ( ᐛ )ᕗ Jimyag&#39;s Blog</title>
    <link>https://jimyag.com/blog/software-design/</link>
    <description>专注于 Kubernetes、KubeVirt、OVN 和 Firecracker 的后端开发工程师</description>
    <generator>Hugo</generator>
    <language>zh-CN</language>
    <copyright>Copyright © 2019, jimyag.</copyright>
    <lastBuildDate>Sun, 09 Aug 2026 23:35:35 +0800</lastBuildDate>
    <atom:link href="https://jimyag.com/blog/software-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>如何编写一份有效的软件设计文档</title>
      <link>https://jimyag.com/posts/write-effective-design-doc/</link>
      <pubDate>Sun, 09 Aug 2026 23:14:32 +0800</pubDate>
      <guid>https://jimyag.com/posts/write-effective-design-doc/</guid>
      <description>从项目或功能的风险、错误决策的代价和评审目标出发，说明如何在 Design Doc 中写清目标、API 契约、状态模型、兼容迁移、失败恢复和验证方案。</description>
    </item>
  </channel>
</rss>
