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
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
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
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
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
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.