Tags
Writing, research, projects, and photos around “Technical Planning”.
Content, search, commerce, and growth systems repeatedly face the same challenge across multiple countries, industries, and scenarios: how to reuse stable capabilities while keeping business expressions distinct. How should boundaries be drawn between configuration, protocols, components, and orchestration?
Short
12 min read
Part of the column “Technical Systems” · Chapter 8
Starting from the different questions asked by analysis, operations, and engineering, this article organizes how a data center for a multi-source business platform should divide Tabs, define metrics, structure read and write paths, and handle billing, reconciliation, growth, and cost.
Short
22 min read
Starting from a multi-system integration experience, this essay distinguishes creation, task efficiency, organizational productivity, and business value—and asks where value and cost actually come from when AI enters a complex system.
Short
5 min read
Part of the column “Engineering & AI Judgment” · Chapter 10
Technical planning is not a project list. At its core it is two things: understanding the business you serve (business analysis) and understanding the gap and level against competitors (competitive analysis), then linking them into a causal chain of goals, trade-offs, and execution.
Short
16 min read
Part of the column “Technical Systems” · Chapter 1