Avoiding the ‘Air‑Castle’ Mindset: How Architects Combine Macro Vision and Micro Detail

After a technical design presentation that fell short of expectations, the author felt uneasy despite positive feedback, recognizing a lingering sense of being "floating in space." A personal post‑mortem identified the core issue as an overly abstract, high‑level approach.

Strengths

In the first month with a new team, the author built a top‑level logical framework, gaining a global view that sometimes surpassed the business analysts' understanding of the domain.

Business analysis: described the product's core business, inter‑departmental collaboration, revenue, customer segments, and transaction volume.

System analysis: examined current module architecture, technical standards, sub‑unit details, deployment topology, and production metrics such as TPS.

Target strategy: derived technical requirements and challenges from the business and technical characteristics.

Technical solution: drafted high‑level functional designs and flowcharts.

Weaknesses

Although the overall analysis was solid, the author questioned why self‑judgment persisted. The fourth part – the technical solution – was too coarse, staying at theory and process level without concrete guidance for developers. It was an overview design , not a detailed design that includes data structures, functional specifics, or class diagrams.

The author stresses that a system‑level architecture must provide detailed designs that developers can follow, covering data models and field definitions to uncover core business functions.

From personal experience, the next steps involve diving into specific data models, mastering table fields, and identifying the core of each business function, thereby achieving deep domain mastery.

Quoting Zhang Jianfei from *Programmer's Underlying Thinking*, the author notes that mastering a new field typically takes about a month: first grasp the macro concepts, then move to code‑level details.

The concluding insight is that only by combining top‑down macro cognition with bottom‑up micro detail can an architect truly claim mastery of a domain, especially under tight timelines that require self‑regulated work pace.