The interview with Fiona Fung reveals how Anthropic’s Claude Code boosted engineer output eight‑fold, reshaped coding from a bottleneck to a ubiquitous skill, and forced teams to rethink verification, agency, accountability, and the loneliness that arises when working alongside AI agents.
This article examines the distinction between project and product managers, outlines the high‑standard qualities required of product managers, describes the ideal career pathways and ability models, and details a resource‑pool framework for systematically developing product‑manager talent within an IPD‑driven R&D organization.
The article outlines five tell‑tale signs of a dysfunctional technical team—impulsive tech decisions, a one‑person tech leadership, chaotic multi‑head management, obsessive process formalism, and a performance‑over‑substance culture—warning engineers that such environments waste time, erode skills, and may merit leaving.
Many engineers consider moving into management because they are tired of coding, but the article explains that management brings its own complexities, requires a shift in responsibility, and should only be pursued after honest self‑assessment and small experiments.
The article argues that the rise of AI‑driven code generation demands a three‑stage Software Engineering 3.0 methodology—context, steering, and knowledge engineering—to turn massive efficiency gains into trustworthy, scalable production systems, making it essential for competitive enterprises.
The article argues that technical managers should evaluate opportunities based on decision‑making scope, complexity, and autonomy rather than simply the size of the company, outlining concrete criteria and signals to identify platforms that truly foster managerial growth.
The article examines the technical and human challenges of turning a simple IMU‑based head‑controlled wheelchair prototype into a reliable, everyday mobility solution for a high‑level spinal‑injury patient, highlighting sensor noise, environmental variability, user‑specific adaptations, and the broader lesson that engineering should serve concrete, real‑world problems.
In two weeks the QQ Browser team used AI‑driven CodeBuddy to let a non‑coding product manager create a loan‑repayment calculator, then generalized the workflow into a reusable template, added Git‑based versioning, command‑line automation and preview tools, ultimately launching 23 small utilities and boosting efficiency by over 370%.
The 2025 AI+ R&D survey reveals that 89.2% of Chinese software teams have embraced large language models, with 62.8% actively using them, driving vertical adoption, significant cost and productivity gains, while also highlighting eight key challenges and a shift toward AI agents.
The article compiles several highly up‑voted Zhihu answers explaining why only a small fraction of programmers become software architects, highlighting differences in mindset, the limited need for architects in small teams, career trade‑offs, and the practical challenges of gaining high‑scale architecture experience.
After structuring and decomposing requirements, this article explains how to define clear, standard value‑stream processes for each demand layer, use a software‑factory platform to drive state‑based automation, and ensure seamless, compliant value delivery from user, system, and software demands to final closure.
The article examines Xerox PARC’s groundbreaking inventions, the open‑culture that fostered them, why Xerox failed to commercialize most of them, and how the shift from closed to open innovation explains the lasting impact of PARC on modern computing.
This article summarizes key insights from “Documents: The architect’s programming language,” explaining why documentation acts as an architect’s programming language, outlining core principles, practical writing techniques like bullet points, headers, and avoiding wall‑of‑text, and showing how to organize, review, and share high‑impact documents throughout a project’s lifecycle.
Even as AI agents become commonplace, the article argues that skilled engineering managers are still essential for bridging technology and business, guiding development teams, handling interpersonal challenges, and ensuring that software delivers real customer value.
This article explores four fundamental thinking patterns—control mindset, leverage mindset, endgame mindset, and closed‑loop mindset—that technical managers should adopt to lead teams effectively, make strategic decisions, and continuously improve both themselves and their organizations.
This article outlines the evolution of DevOps standards, organization‑level capability building, AI‑enabled R&D and operations, and the foundational AI‑driven assurance framework, highlighting recent assessments, standards, and industry adoption across finance, telecom, manufacturing, and other sectors.
The article reflects on the pitfalls of applying a single, static strategy to cross‑department initiatives, shares a three‑step pilot‑to‑scale model for early stages, and proposes three adaptive tactics—targeted focus, breakthrough tackling, and gap‑filling—for mature phases, emphasizing flexible, goal‑layered management.
This article explains how a project team tackled the challenges of entering a new business domain by replacing rigid, one‑size‑fits‑all controls with a dynamic, LEGO‑like management mechanism that evolved through four versions—chaos, layered, contraction, and attack—resulting in faster alignment, risk pre‑positioning, and collaborative evolution.
The article introduces the concept of a decision fractal, showing how each step of analysis, planning, execution, and reflection contains smaller nested cycles, forming a self‑similar structure that transforms linear decision chains into adaptable, scalable processes.
This article gathers engineers’ experiences and advice on selecting open‑source licenses, explaining GPL’s contagion risk, comparing permissive (MIT/Apache) and copyleft (GPL/LGPL) options, and offering practical guidelines for balancing technical freedom with commercial security across different project scenarios.
While Agile offers structured, fast‑feedback cycles ideal for commercial product delivery, the Bazaar model thrives on voluntary, decentralized contributions that fuel disruptive innovation; this article compares their principles, advantages, challenges, and suitable scenarios, helping teams decide when to adopt or blend each approach.
In the AI era, developers must shift from merely writing code to mastering soft skills such as problem definition, cross‑functional collaboration, and critical thinking, using AI tools as assistants while maintaining rigorous quality checks and clear communication to create real business value.
This article shares practical principles for software developers to transcend pure coding by respecting users, optimizing processes, enhancing collaboration, providing supportive management, and designing flexible, maintainable code, ultimately improving team efficiency and product quality.
The article examines a real production incident, highlights how a proactive manager turned the crisis into a learning opportunity by soothing customers, reporting transparently, and then systematically analyzing team processes and management responsibilities to prevent future issues, illustrating the broader principle that danger and opportunity coexist.
This article explores why vision is a crucial, psychologically driven element in management, illustrates its role through examples like Google and SpaceX, explains how even small technical teams benefit from a clear vision, and concludes with a promotional notice for a DevOps engineering certification.
The article outlines the essential competencies, responsibilities, and end‑to‑end workflow—including initiation, design, testing, production, and risk control—that a project manager must master to successfully lead smart‑hardware development projects in manufacturing.
This article presents a comprehensive set of agile and R&D process metrics—including delivery cycle, team productivity, sprint throughput, integration frequency, technical debt, and test coverage—detailing their definitions, calculation formulas, recommended improvement actions, and normal versus warning ranges to help engineering teams monitor and enhance performance.
James Samuel shares five actionable strategies—clarity, strong team composition, synergy, empowerment, and continuous improvement—to transform struggling software groups into high‑performance R&D teams, emphasizing clear goals, stable sizing, collaborative culture, autonomous ownership, and regular reflection.
This guide explains how test developers can efficiently complete diverse testing tasks by understanding task requirements, communicating details, classifying tasks, using visual and questioning techniques, preparing appropriate tools, executing work with structured processes, and reflecting on outcomes to turn experience into reusable skills.
This article describes how KooJiaLe, a leading 3D design company, built an AI‑powered platform that uses large language models to automate test case generation, detailing its workflow, generation modes, editing features, export options, optimization efforts, results, and remaining challenges.
IBM China abruptly removed access for more than a thousand research and testing staff, signaling a sudden, large‑scale layoff that coincides with the company's aggressive push into generative AI, cloud services, and a broader global restructuring effort.
This article presents five key R&D efficiency dashboards—covering requirements, project progress, incidents, risks, and defects—designed for CTOs to monitor software development quality, along with a curated list of further reading on metrics and best practices.
This article outlines an architect's thinking model, a step‑by‑step requirement analysis, core design principles for a risk engine—including efficient rule composition, operational support, unified SDK integration, and an event ingestion center—and presents business, application, data, and technical architecture diagrams to illustrate the complete system.
This guide outlines a comprehensive hardware R&D quality management process—from project initiation and requirement analysis to design reviews, testing, SPC, FMEA, and cost management—ensuring product reliability, stability, and competitive market performance.
This guide outlines twenty essential hardware development, security, and reliability performance indicators—such as development cycle, defect density, security certification rate, MTBF, and supply‑chain safety—and provides practical measurement methods to help engineers quantify and improve product quality and safety.
An illustrated guide walks you through the five essential phases of the R&D lifecycle—Concept, Planning, Development, Verification, and Release—showing key activities at each stage and linking to further resources on metrics, standards, and best practices for effective product development.
The article examines why rewarding partial achievements and hard‑working teams is essential for morale, fairness, and long‑term performance, using real‑world cases to show the pitfalls of result‑only evaluation and proposing balanced incentive mechanisms for R&D groups.
The article analyses the low efficiency problems faced by Chinese SaaS firms across product, development, customer acquisition and after‑sales, identifies root causes such as homogenous offerings, poor demand management, weak R&D processes, and proposes strategic, cultural, architectural, procedural and metric‑driven solutions to boost overall performance.
This article explains how managers can nurture genuine creativity among software engineers by focusing on technical knowledge, collaborative environments, balanced constraints, critical thinking, curiosity, and practical tools, turning creativity into a trainable skill rather than a myth.
The article classifies five distinct types of outlier employees in technical teams, outlines five red‑line rules for managers, and offers practical guidance on how to embrace diversity, set clear boundaries, and handle such staff through open communication, appropriate reassignment, or decisive action when necessary.
This article traces the evolution of OKR in Chinese internet giants—from its 2013 introduction and peak popularity to its recent decline and conflation with KPI—while highlighting management theory origins, employee experiences, and concluding with a promotion for the IDCF DevOps conference.
This article outlines a structured approach for R&D managers to lead quarterly retrospective meetings by asking four key question groups—result, process, gap, and improvement—each broken down into specific sub‑questions that help uncover issues, analyze causes, and define actionable plans for continuous performance enhancement.
Developers often struggle with vague OKR metrics, so this article outlines a comprehensive framework—grounded in first principles—to define, measure, and achieve developer OKRs by focusing on efficiency, quality, sustainability, and clear, objective metrics that align with business goals.
This article, based on an interview with Huolala's database leader Cai Peng, outlines essential criteria for selecting database tools from both developer and DBA perspectives, compares small‑scale versus comprehensive solutions, and emphasizes the need for integrated, platform‑level tooling in modern cloud‑driven environments.
The article presents a framework for measuring and enhancing R&D value by combining business and technical value, optimizing effective time, and minimizing abnormal and normal costs through strategic prioritization, streamlined processes, engineering automation, and disciplined cost‑control practices.
This article explains how applying the SMART framework—Specific, Measurable, Achievable, Relevant, and Time‑bound—helps teams define clear, actionable goals, differentiate measurable KPIs from broader KRAs, and avoid common pitfalls such as vague objectives or resource‑driven targets.
The article analyzes TSMC’s extraordinary growth since its 1994 IPO, highlighting its high profit margins, massive patent portfolio, diverse process technologies, dominant customer base, expanding market share in wafer foundry, massive capital investments, and its pivotal role in the global semiconductor ecosystem.
The article explains how to prepare for successful organizational change by creating urgency and recognition, establishing a change leadership team, guiding team participation, defining clear goals, conducting research interviews, and developing detailed action plans, all supported by practical examples and visual illustrations.
This article examines CoolHome’s shift from a tiered to a graded project‑initiation process, detailing the motivations, the criteria for each model, the challenges of the tiered approach, and how the graded system improves decision‑making, resource allocation, and strategic alignment.
The article explains how habitual inertia hampers innovation and presents two systematic approaches—first‑principles thinking and the four‑action framework—to help technical teams break old habits, redesign processes, and achieve continuous improvement and creative breakthroughs.
This article describes JD Supply Chain's self‑developed low‑code rule engine platform, outlining its motivation, high‑concurrency performance challenges, value‑centric design, visual rule‑authoring workflow, SDK integration, and the resulting efficiency gains for both development and business teams.
The article compares a large, waterfall‑style, client‑driven project (Project A) with a business‑centric, agile project (Project B), highlighting how agile practices such as continuous collaboration, iterative testing, and value‑driven development lead to higher software quality, faster delivery, and happier teams.
Alibaba has reorganized its technology leadership by eliminating the group CTO position, merging core tech teams into subsidiaries like Aicheng Technology, and shifting its "big middle platform" strategy toward more agile front‑end structures, signaling a broader move toward decentralized, product‑centric engineering.
This article outlines a three‑level problem‑solving methodology—emergency response, deep analysis, and pursuit of excellence—providing technical managers with concrete steps, communication templates, and real‑world SaaS examples to boost team performance and drive continuous improvement.
Tencent’s 2022 R&D report shows that three‑quarters of its staff are developers, with over 7,000 new projects, 29.4 billion new code lines, and a 60 % reduction in build time after moving to cloud‑native DevOps, while Go tops language usage and open‑source contributions exceed 80 %.
This article compiles a hundred concise observations on industrial software development, covering technology valuation, coding practices, design focus, market dynamics, open‑source usage, solver development, numerical methods, and industry trends, while also promoting the IDCF DevOps Hackathon event.
This article explains the history and principles of OKRs, outlines a step‑by‑step process for defining a technical department’s purpose, identifying internal customers and their needs, reviewing past OKRs, and establishing practical guidelines for drafting, iterating, and communicating new OKRs.
This article explains how to build a comprehensive indicator system for project management by applying the OSM (Object‑Strategy‑Measure) model, detailing the six essential elements of each metric, domain segmentation, and continuous improvement to align technical and business goals.
This article compiles the latest salary offers, benefits, and ranking tiers for Chinese military research institutes, explains how to evaluate and choose among them, and compares these positions with other industries to help engineers make informed career decisions.
This article details how the Vivo Internet Platform product R&D team introduced the Objectives and Key Results (OKR) framework, the challenges they faced before its adoption, and the six major improvements—including clearer goals, value‑focused challenges, enhanced collaboration, a stronger learning culture, continuous innovation, and higher employee productivity—that resulted from the OKR implementation.
By adopting OKR, Vivo’s Internet Platform R&D team aligned strategic goals, prioritized high‑value initiatives, streamlined collaboration through the HuoLi platform, fostered a robust learning culture, spurred internal innovation, and boosted productivity, creating a virtuous flywheel that positions the team as a self‑organizing, high‑performance benchmark.
This article guides R&D team leaders through the mindset, stages, implementation steps, application patterns, common challenges, and future directions for adopting low‑code platforms to reduce costs, improve efficiency, and solve specific business problems.
This article explains the ten advantages of using fixed‑length agile iterations—such as better forecasting, risk control, reduced waste, and improved alignment—while highlighting common pitfalls like extending iterations, treating them as mere timelines, and unstable team composition, emphasizing the prerequisites needed to reap these benefits.
The article argues that software development should adopt the lean production and value‑stream principles used in physical product manufacturing, highlighting the rising complexity of software in products like cars and urging organizations to treat software as a continuous product flow rather than a short‑term project.
This article recounts a company's shift from traditional project management to agile practices, detailing demand grooming, sprint planning, daily stand‑ups, iteration reviews, retrospectives, and the integration of a simple three‑state Kanban board within TAPD to handle uncertain work and improve continuous delivery.
The article outlines the definition, essential elements, types, and step‑by‑step process of communication within organizations, and proposes formal and informal mechanisms—including meetings, 1‑on‑1s, weekly reports, and knowledge platforms—to improve information flow, alignment, and team cohesion for better management outcomes.
This article explains how technical managers can improve ROI by systematically collecting information, defining clear goals, prioritizing tasks, evaluating alternatives, avoiding common cognitive biases, and using tools such as RACI matrices and continuous process control to execute and refine decisions.
In this article, a tech leader shares ten concrete practices—from delegating authority to group leads and building personal trust, to handling on‑call releases and protecting subordinates—that have helped him effectively manage a diverse 100‑plus‑person engineering organization.
The article explains Amazon’s Two‑Pizza team model, emphasizing its core principles of autonomy, responsibility and entrepreneurial spirit, detailing team composition, management practices such as mission‑driven press releases and fitness‑function metrics, and evaluating its advantages and limitations for scaling innovation.
This article shares practical guidance on identifying common project risks and outlines five essential practices—comprehensive design, schedule buffers, embracing requirement changes, daily risk synchronization, and detailed launch planning—to help teams manage risks and keep projects on track.
The article explains how establishing team consensus on the purpose and baseline of retrospectives, understanding the two main retrospective approaches, and equally analyzing both strengths and weaknesses while focusing on key factors and deep analysis can prevent blame culture and improve learning outcomes.
This guide explains the purpose of weekly reports, outlines how to tailor them for supervisors, teams, and personal reflection, and provides structured templates, the STAR principle, and efficiency tips to help technical managers write clear, data‑driven, and actionable reports.
Tencent’s 2021 R&D report uncovers a 41% rise in engineering staff, 6,000+ new projects, 3.2 billion added code lines, a surge in Go usage, extensive open‑source contributions, and a bold carbon‑neutrality roadmap, offering a comprehensive view of the company’s technical momentum and industry impact.
Tencent’s 2021 R&D Report details a 41% rise in engineering staff, 32 billion new code lines, Go becoming the top language, massive growth in open‑source contributions, breakthroughs in cloud OS, databases, AI, and a commitment to carbon‑neutral technology‑driven social impact.
This article analyzes the mismatched organizational design between banking technology and business units, explains why traditional “technology serves business” models fail, and proposes four practical assessment‑based solutions to create a balanced, collaborative relationship that supports modern fintech demands.
This article analyses the current state of China's industrial software—covering EDA, CAD, and CAE markets—highlighting domestic market shares, the dominance of foreign giants, development difficulties, misconceptions, and the key factors that hinder the growth of home‑grown solutions.
The article explains five distinct agile coaching postures—coach, lecturer, mentor, consultant, and role model—detailing when to adopt each, how to transition between them, and the importance of maintaining neutrality while guiding teams toward self‑directed improvement.
This article outlines six practical metrics—unified backlog, user‑centric requirement description, consistent requirement flow, short lead time, high iteration completion rate, and stable iteration velocity—to help teams distinguish superficial agile ceremonies from truly effective agile execution.
The article outlines a three‑stage roadmap—Innovation 1.0, 2.0, and 3.0—detailing how large enterprises can systematically build, scale, and sustain innovation through strategic alignment, cultural cultivation, diversified innovation models, closed‑loop mechanisms, and ecosystem partnerships.
The article explains how agile teams can thrive amid VUCA conditions by aligning clear goals, fostering intrinsic motivation, and developing diverse capabilities, offering practical management principles and four key practices—goal transparency, capability building, self‑organization, and motivation extraction—to achieve high‑performance outcomes.
This article introduces essential project management concepts, including the five process groups, demand review, risk identification, scheduling, and reporting, to help software developers improve coordination, communication, and overall efficiency in their development workflows.
This article examines the hidden mental models that constrain business developers, explains why their self‑perception often mismatches evolving environmental demands, and outlines a step‑by‑step framework for shifting from a code‑centric role to a holistic technical‑lead position that drives customer digitalization.
In this talk, former Amazon and Alibaba chief architect Chen Hao shares practical ideas on why high‑efficiency teams matter, how to create them through people selection, processes, leadership, and automation, and offers concrete management tactics such as clear goals, small‑team structures, and data‑driven decision making.
This article shares a practical six‑step framework—from understanding nervousness and defining purpose to designing simple slides, crafting a script, deliberate rehearsal, and handling Q&A—to help technical newcomers deliver confident, audience‑focused presentations at conferences.
This article presents a comprehensive team management framework built from the ground up, outlining two overarching dimensions and ten distinct modules—ranging from time and project management to talent recruitment and team building—to help organizations systematically improve their management practices.
This article explains how GrowingIO's R&D department structures project classification, work, personnel, and time management using Jira, detailing requirement handling, iteration processes, and practical Scrum/Kanban practices to balance OKR goals with customer demands.
The article reflects on developers’ tendency to create custom frameworks—driven by interview pressure, ego, and perceived career benefits—while warning that such efforts often waste effort on low‑value code assembly and may hinder real skill growth and professional advancement.
In his May 2021 address to the Chinese Academy of Sciences, the Chinese Academy of Engineering, and the China Association for Science and Technology, President Xi Jinping stressed the strategic importance of scientific self‑reliance, outlined achievements in basic research, high‑tech industries, and defense, and called for deeper reforms, talent cultivation, and global cooperation to build a world‑class innovation system.
This article explains why planning is essential for every team, outlines two core thinking modes—inductive and deductive—and shares four practical planning methods (similar‑thinking, dimensional‑thinking, reduction‑thinking, and specialization) to help practitioners create focused, actionable, and measurable roadmaps.
The author reflects on a decade at Google, sharing how exposure to a diverse, innovative environment reshaped his views on differentiation, transformed his technical mindset from user to owner, and revealed unconventional management practices that emphasize empowerment, tool‑driven processes, and the pursuit of joyful, purpose‑driven work.
Tencent’s 2020 R&D Big Data Report shows the company added 2 billion lines of code, with R&D staff comprising 68% of its workforce, highlights C++ as the top language, details significant efficiency gains, and reveals high‑quality code output from technical leaders and senior engineers.
In this reflective guide, a newly appointed CTO shares his career timeline, defines the CTO role, adapts a proven framework, and outlines fourteen practical lessons—from self‑belief and time management to delegation, handling chaos, and making smart decisions—to help technology leaders thrive.
In his 2019 GeekPark Innovation Conference talk, Pixar co‑founder Ed Catmull explains how a culture of equal, candid Braintrust meetings, embracing productive failure, and rapid iteration transformed Pixar’s creative process and later revitalized Disney Animation, offering practical lessons for managing innovation in any organization.
This satirical guide lists seven counterproductive tactics—like hiring big‑company talent for a startup, misusing agile, ignoring proper role ratios, over‑managing, false startup culture, line‑count performance metrics, and unnecessary middle‑platforms—that can cripple a small software team.
The article shares a CTO’s personal journey from architect to technology leader, emphasizing the importance of empathy, disciplined communication, decisive judgment, building a distinctive team, aligning vision and mission, and fostering a healthy organizational culture to drive effective execution and sustainable success.
China’s electronic information federation released a detailed competitiveness index for software and IT service firms, highlighting five performance tiers, rapid revenue growth, strong R&D investment, expanding global exports, and the sector’s pivotal role in digital transformation and national strategic goals.
The article humorously outlines seven destructive tactics—such as poaching talent from big firms, misapplying agile, enforcing unrealistic role ratios, neglecting proper technical management, promoting false startup culture, using line‑count performance metrics, and building unnecessary middle‑platforms—to illustrate how to deliberately cripple a small‑to‑mid‑size tech team.
The article reflects on how most members of technical teams are passively driven, examines the unsustainable management practices that try to force active drive, draws parallels with education and economic sustainability, and proposes a more balanced, sustainable team culture that respects individual differences and long‑term growth.
This article examines common misconceptions about software architecture, explains that its core purpose is to manage system complexity, offers practical guidance for identifying complexity hotspots, and presents a concrete university student‑management system case study to illustrate effective architectural decision‑making.
The article explains what a software architect is, outlines their evolving responsibilities across development phases, describes various architect specializations, highlights essential skills and team collaboration practices, and offers career guidance for aspiring architects.
