Focused on fintech, sharing experiences in financial services, architecture technology, and R&D management.
The article demystifies why many users get disappointing results with AI by detailing the essential concepts—Tools (local and remote), the Model Context Protocol (MCP), Rules, Skills as reusable recipes, and the different Agent types—so readers can precisely describe tasks and fully leverage AI capabilities.
The article explains how architects can bridge high‑level platform diagrams and concrete implementation by using DDD‑based module functional diagrams that serve as prompts for AI code generation, avoiding low‑level detail while ensuring domain understanding guides development.
This article compares OpenCode with Codex and Claude Code, explains why OpenCode is the lowest‑barrier AI agent for ordinary users, and provides step‑by‑step installation instructions for its desktop, VSCode plugin, and CLI versions on multiple operating systems.
The article outlines a practical, four‑step process for architects to fully understand and redesign an aging legacy system, covering business knowledge, the four core functional modules, comprehensive data‑model analysis, and handling of business exceptions, while noting the limited role of AI assistance.
The article analyzes the fundamental differences between commercial bank financial market products such as Jicun Jin and traditional transaction‑banking services, covering client segments, the definition of a transaction, and the distinct market‑risk exposure each model entails.
The author reflects on a recent technical design presentation, analyzes strengths and gaps in the architecture process, and argues that only a top‑down macro view paired with bottom‑up micro‑level detail can prevent architects from drifting into vague, non‑actionable designs.
The article explains the definition, risk‑weighting methodology, and tiered structure of capital under the 2024 Commercial Bank Capital Management Measures, presents the regulatory minimums, and analyzes 2025 data for state‑owned and joint‑stock banks, highlighting strengths and emerging capital pressures.
The article argues that an architect’s worth is measured by the business outcomes their systems enable rather than internal code elegance, citing AI‑generated code, the Taobao development story, and sales‑driven revenue as evidence that external value outweighs internal craftsmanship.
The article explains how commercial banks must set aside deposit reserves and provision funds—mandatory reserves locked with the central bank and daily liquidity kept for operations—and how gold‑backed deposit products add complexity, illustrating why only the remaining funds are truly free for the bank to deploy.
The article examines whether services must adhere to strict layered calls in DDD, explains the layered‑to‑COLA refinement, describes the “sinkhole” anti‑pattern caused by excessive pass‑through interfaces, and offers criteria such as the 80‑20 rule for deciding when to open a layer.
