<?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>Clean Architecture on Peter.H's Full-Stack GAME</title><link>https://peter-notes.com/tags/clean-architecture/</link><description>Recent content in Clean Architecture on Peter.H's Full-Stack GAME</description><image><title>Peter.H's Full-Stack GAME</title><url>https://peter-notes.com/images/og-image.jpg</url><link>https://peter-notes.com/images/og-image.jpg</link></image><generator>Hugo</generator><language>zh-tw</language><lastBuildDate>Sun, 04 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://peter-notes.com/tags/clean-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>同樣的功能，為什麼 Flutter 比 Vue 難 Debug 十倍？從實戰到架構的六層反思</title><link>https://peter-notes.com/posts/flutter-vs-vue-debugging-complexity/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://peter-notes.com/posts/flutter-vs-vue-debugging-complexity/</guid><description>同樣是「關於我們」頁面的顯示邏輯，Vue 改了十幾個 commit 都很順利，Flutter 卻卡了很久。本文從 Debug 實戰出發，延伸到 Domain Model 的防禦能力、Clean Architecture 的責任邊界、扁平架構的取捨、BFF 的可靠性價值，最後探討交接代碼的信任陷阱。</description></item></channel></rss>