This article explains what an Architecture Committee is, why enterprises need one, its typical composition, decision processes, daily operations, common pitfalls, and key success factors for effective enterprise‑level architecture governance.
The article introduces Matt Pocock's open‑source "skills" collection for AI coding agents, shows how it embeds traditional engineering practices such as alignment, domain modeling, TDD, and architecture governance into reusable command sets, and walks through a complete partial‑refund feature implementation using these skills.
The article analyzes current AI code agents such as Claude Code and Cursor, highlights their three major limitations—guessing relationships, staying within the code domain, and lacking a temporal dimension—and proposes UModel’s deterministic AST extraction and cross‑domain linking to create a native code knowledge graph that lets agents move from merely finding code to truly understanding its structure.
This article explains how TOGAF’s process framework and ArchiMate’s visual modeling language can be combined to create clear, standards‑based architecture views that bridge strategy, business, application, and technology layers, offering concrete steps, common pitfalls, and tool recommendations for effective enterprise architecture governance.
The article argues that a CIO who can only talk about system uptime and architecture without translating technical outcomes into financial impact will be seen as a cost center, and outlines four dimensions—organizational influence, architecture governance, resource scheduling, and AI awareness—to upgrade the CIO into a profit‑driving business architect by 2026.
The article breaks down the CEO’s five core expectations for a CTO—business‑impact levers, clear ROI, rapid incident decision‑making, team efficiency metrics, and AI strategy—and shows how most CTOs currently meet only a fraction of these, urging a shift from pure technical expertise to technology‑business stewardship.
CTOs who hide behind technical complexity and refuse to link their initiatives to measurable business outcomes risk losing influence, budget, and decision‑making power as 2026’s enterprises demand clear ROI, prompting a shift toward result‑oriented architecture governance, decision loops, and concrete reporting practices.
The article shows how technology leaders can turn technical proposals into clear business outcomes by using a three‑layer value‑translation framework, architecture governance models, resource‑allocation tactics, and organizational influence strategies, illustrated with real‑world e‑commerce case studies and Gartner data.
The article explains how technical team chaos usually stems from a CTO’s loss of focus, outlining three progressive loss‑of‑control paths—organizational control drift, technical decision drift, and architecture governance gaps—and offers a 2026‑ready governance framework with concrete metrics, tools, and processes.
The article outlines the challenges of distributed architecture governance and presents a layered decision framework, ADR usage, technology radar, committee structures, tooling, and continuous improvement practices to achieve consistent yet innovative architectural standards.
The article details Kuaishou architect Zhao Qingjie’s analysis of B‑end business challenges versus C‑end, outlines the multi‑dimensional governance covering service, business, storage and disaster‑recovery layers, and explains how systematic quality‑assurance, monitoring, error‑code design and organizational mechanisms dramatically improved system stability.
This article details Kuaishou's engineering architecture governance process, covering project background, IDEA performance bottlenecks, cloud‑based IDE solutions, MavenHelper and custom Maven plugins for dependency analysis, handling NoClassDefFoundError issues, and static‑dynamic class dependency detection to improve backend build efficiency.
The article examines a company's struggle to justify the ROI of Enterprise Architecture after replacing ERP, outlines common misconceptions about EA costs and value, and proposes a disciplined, strategic‑level approach using the 5W2H method to achieve high benefits with limited investment.
The article explains the recently released TOGAF 10, highlighting its modular, topic‑centric structure, the various audiences and roles that can benefit from it, the core documents and series guides, and concrete examples of how different practitioners can apply the framework in their organizations.
This article explains how measurement (SLI/SLO), governance (architecture refactoring, MTTx), and validation (chaos engineering, disaster drills) interrelate in microservice systems, illustrating how observability drives governance actions, governance improves metrics, and validation reinforces both through continuous testing.
This article reflects on the often‑overlooked discipline of enterprise architecture, highlighting common mistakes such as treating EA as a purely technical function, short‑term focus, executive arrogance, and over‑reliance on outdated frameworks like TOGAF, and proposes using data‑driven, metacognitive tools to guide more valuable, lightweight, and automated architectural practices.
This article explores how large language models can be integrated into software architecture governance, turning architectural rules into code, enhancing design, development, and runtime phases, and improving code generation quality through explicit knowledge, DSLs, and full‑process AI assistance.
The article outlines the various enterprise architecture roles defined by Disciplined Agile, explaining each role’s responsibilities—from Enterprise Architect and Chief Enterprise Architect to Architecture Owner, Chief Architect, and numerous specialist architects—while also providing a detailed table of specialist architect types and their focus areas.
This article explores the concept of architecture autonomous services as a self‑service data platform for architecture governance, outlines a four‑stage roadmap, provides concrete Log4j tracking examples using SourceGraph and ArchGuard, and details practical steps to build a data foundation, abstract service interfaces, integrate BI, and design metric‑driven evolution.
This article explores a practical approach to enterprise architecture governance by defining patterns, documenting standards, formalizing rules, and using tools like ArchGuard to detect code and architectural smells, visualize issues, and evolve compliance through measurable metrics.
The January 8th Shanghai salon, co‑hosted by DeWu Technology and Juejin, gathered e‑commerce experts to discuss peak‑season stability, emphasizing balanced mid‑platform development, link governance, rapid recovery, cross‑functional collaboration, and architecture governance through global visibility, measurement, and control of services and technical environments.
This article explores the challenges faced by tech teams in fast‑changing, VUCA‑driven markets and proposes an entrepreneurial approach—strong belief, clear vision, value‑chain thinking, disciplined architecture, and a pragmatic team culture—to activate technical competitiveness and sustainable growth.
The article provides a comprehensive overview of TOGAF’s architecture capability framework and governance model, detailing how enterprises can build, govern, and mature their architecture functions through organized processes, roles, resources, and compliance mechanisms across multiple architectural domains.
This comprehensive guide explains how TOGAF’s Architecture Capability Framework helps enterprises build and govern architecture capabilities, covering governance structures, capability components, the ADM phases, architecture committees, compliance processes, and practical governance guidelines for successful enterprise architecture implementation.
The article explains the responsibilities, strategic influence, and collaborative practices of Enterprise Architects within SAFe, highlighting how they drive adaptive design, portfolio governance, cross‑solution coordination, and continuous improvement to align technology decisions with business goals.
This article examines JD Pay's business architecture transformation, detailing the drivers behind the change, the challenges of large‑scale system migration, the new platform's architectural goals, implementation steps, and the measurable outcomes that improved stability, scalability, and data insight.
