Columns
Technical Systems
Technical planning as business and competitive analysis: reading the business and the gap to rivals, then turning them into sound architecture, standards, and code.
- Chapter 1 · Short · 16 min read
Technical Planning Is Fundamentally Business Analysis and Competitive Analysis
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.
- Chapter 2 · Short · 2 min read
Why Code Decays: From Local Convenience to Systemic Debt
Code decay rarely comes from any single moment of bad writing; it comes from local changes repeatedly bypassing shared boundaries. What truly needs maintaining is the consistency between design and collaboration.
- Chapter 3 · Short · 2 min read
How Engineering Standards Reduce Rework Without Creating Bureaucracy
Good standards don't turn every step into an approval; they make the key handoff points — where distortion, rework, and accidents are most likely — visible, discussable, and reusable.
- Chapter 4 · Short · 3 min read
Shared Core and Local Variation: How Multi-Region Systems Evolve
A multi-region system can neither cram every difference into a single core nor rebuild everything for each region. The key is to identify stable boundaries, preserve extension points, and clarify module ownership.
- Chapter 5 · Short · 2 min read
After AI Acceleration: How to Redraw Functional and Business Lines
Functional lines once made specialized capability run efficiently; once tools lower workflow barriers, organizations should redesign around end-to-end business capability rather than cling to historical divisions of labor.
- Chapter 6 · Short · 19 min read
From One Request to a Multi-Node Execution System: How the Architecture Evolves
Starting from the fault structure of a multi-node execution system, this article reviews how requests, state, storage, performance, and failures gradually cross boundaries, and discusses how the next architecture should be reorganized.
- Chapter 7 · Short · 13 min read
Where Exactly Is the Cache? Locality in a Multi-Layer Execution Service
Using a multi-layer execution service as an example, this article breaks down the multiple levels of locality across request identity, edge routing, execution resources, and backend caches, then presents reusable approaches to routing, invalidation, failover, and observability.
- Chapter 8 · Short · 12 min read
Keeping Differences at the Configuration Layer: Architecture for a Multi-Domain Platform
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?
- Chapter 9 · Short · 16 min read
AI Gateway: From Backend Scheduling to Cost Governance
Using multi-backend model access as the setting, this article explains how an AI Gateway handles resource scheduling, capacity control, failure switching, distributed state, usage accounting, and enterprise cost governance.