91 個組件的 Skill 為什麼生不出一個訂單頁面？
開發者常把 Skill 責任範圍設得過大，導致設計出過度複雜的架構。本文拆解 Skill 的 5 層能力邊界,指出其本質是「知識庫」而非「自動化引擎」。
System Design
Why Can’t a Skill with 91 Components Generate an Order Page?
Developers often set a Skill’s responsibility scope too broadly, leading to overcomplicated architectures. This post breaks down the five levels of Skill capability boundaries and points out that its nature is a “knowledge base,” not an “automation engine.”
Why Does One Business Rule Change Break 5 Services? How DDD Solves This
🌏 閱讀中文版本 Have you experienced this scenario: Your product manager says “Support a new discount rule,” and suddenly you’re modifying OrderService, DiscountService, PromotionService, PricingService, and CustomerService. By the time you’re done, you realize this “simple” requirement touched 5 different modules. This isn’t an edge case. It’s a symptom of poor system design. Domain-Driven Design (DDD) … Read more
為什麼改個業務規則要改 5 個地方？DDD 如何解決
“探討領域驅動設計（DDD）如何解決複雜系統中的業務邏輯散落問題。從聚合根、限界上下文、領域事件等核心概念，到後端工程師、產品經理、系統架構師的三角視角，理解 DDD 如何簡化而非複雜化系統設計。”
架構圖箭頭方向的藝術：準確傳達系統設計
隨著技術架構日益複雜，架構圖成為了描述和理解系統的關鍵工具。在之前的討論中，我們已經探討了箭頭方向的基礎知識以及在雲服務平台中的應用。本文將進一步深入，探討在處理大型或複雜系統架構時，如何有效利用箭頭方向表達複雜的網絡和服務關係，以及如何解決常見的問題。 複雜架構中的箭頭方向 在複雜的系統架構中，數據流和服務間的互動變…
The Art of Arrow Direction in Architecture Diagrams: Accurately Conveying System Design
Master arrow direction in architecture diagrams to accurately convey system design intent. Learn to represent data flow, dependencies, and communication patterns for clearer technical documentation and team collaboration in software engineering projects.