Focused on fintech, sharing experiences in financial services, architecture technology, and R&D management.
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.
Architects often view standards as abstract, yet when dealing with diverse stakeholder interests, establishing clear platform architecture standards—identifying key parties, building consensus, and formally publishing the rules—creates enforceable constraints that reduce conflict and give architects authoritative guidance for evolution.
The article outlines a step‑by‑step framework for fintech engineers to quickly acquire deep knowledge of a new business area by mapping people, processes, culture, and technology, using a panoramic business map and targeted learning activities.
The article analyzes the rise of gold accumulation accounts in Chinese commercial banks, explains their business nature, compares them with paper gold and physical gold, presents industry‑wide scale data, traces their development history, and highlights the key technology capabilities banks must build.
The article outlines a practical 7‑step code‑review SOP that leverages IDE static analysis, AI assistance, impact analysis, unit‑test validation, production data checks, non‑functional evaluations, and business‑exception safeguards, enabling banking‑IT teams to achieve two years of zero production incidents.
This article explains the concept of financial exposure in banking, using clear analogies and detailed examples—including consumer loans, corporate credit lines, and regulatory rules—to illustrate how gross and net exposure are calculated and classified across risk types, accounting treatment, and business lines.
This comprehensive guide explains the purpose, core concepts, suitable scenarios, common patterns, benefits, and potential pitfalls of asynchronous processing, offering detailed design, development, review, and operational principles to help teams build reliable, high‑throughput systems.
This article explains the origin and practical meaning of the financial term “position,” illustrates it with everyday analogies, outlines key liquidity and trading perspectives, and provides concrete banking scenarios to help newcomers grasp how banks manage funds and risk.
