In this reflective article, a newly appointed CTO shares a year‑long journey from software engineer to technology leader, outlining fourteen practical lessons on leadership, time management, delegation, decision‑making, and the unique challenges of guiding an IT‑service organization.
This article presents a practical framework for measuring and increasing R&D value by combining business and technical contributions, streamlining processes, investing in sustainable engineering, enhancing individual productivity, and systematically eliminating abnormal costs.
The article explains how enterprises can transition from traditional waterfall development to scaled agile practices by introducing Scrum of Scrums (SOS) architectures and three scaling models—1+1+2N, 1+3N, and 1+4N—detailing their structures, meetings, advantages, and limitations for teams ranging from dozens to hundreds of members.
This article examines the shift to multi‑entity, cross‑stage collaboration in enterprises, outlines the resulting inefficiencies and resource constraints, and presents a three‑step solution—measurement, analysis, improvement—implemented through a unified R&D efficiency management platform that standardizes workflows, integrates OKR and metric dashboards, and drives digital transformation for sustained productivity gains.
The article explains why influence is essential for software testers aspiring to leadership, outlines key personal traits, presents common challenges, and provides a four‑step framework—including non‑violent communication techniques and practical case studies—to help testers effectively drive change and resolve conflicts.
The discussion analyzes Elon Musk's unconventional leadership style, relentless pursuit of high‑intensity challenges, rapid‑failure mindset, and product‑centric strategies, drawing lessons for R&D and product management while contrasting his approach with traditional business practices and cultural norms.
The article examines how technology and business teams can align their objectives, explaining why fast implementation, change responsiveness, and rapid delivery must be balanced with quality, measurable metrics, and clear scope to support stable, profitable operations.
This article explains the rationale, classification, and practical principles for managing technical costs in a company, emphasizing the need to target major cost drivers, apply different strategies per cost type, eliminate wasteful expenses, and maintain a holistic view to support sustainable business growth.
The article examines how software development teams incur hidden cognitive, communication, and abnormal costs, explains their sources such as memory load and technical debt, and proposes practical strategies—including talent selection, shared standards, and incident prevention—to reduce these costs and improve overall R&D efficiency.
The article describes how Autohome established a company‑wide, fine‑grained quality measurement system and a comprehensive quality score model that unifies standards across departments, integrates multi‑source data, and drives continuous optimization to enhance user experience and product reliability.
The article explains the distinct responsibilities of sponsors, project managers, and core team members in project management, highlights common pitfalls such as role confusion, over‑intervention, and poor communication, and offers guidance on how to avoid these issues for successful project outcomes.
This article explains how technical managers and developers can adopt a problem‑solver mindset, apply a structured methodology for diagnosing and resolving issues, and act as clear “voice‑pipes” to convey information responsibly, thereby improving team efficiency, cohesion, and information security.
At the 2023 GOPS Global Operations Conference, China International Capital Corp’s IT team detailed how they passed the Continuous Testing (CT) Level‑3 assessment, sharing insights on building a comprehensive testing framework, improving quality culture, and the strategic impact on their financial services development.
The article examines hiring bias against three‑year college graduates, shares real chat excerpts, and offers a step‑by‑step roadmap for associate‑degree programmers—including continuous learning of algorithms, systems, and big‑data tools, strategic job moves, and mindset shifts—to advance toward senior or leader roles despite initial educational disadvantages.
This article explains what metrics are, categorizes them, describes how to design effective metrics for R&D teams, outlines criteria for judging their quality, and provides practical guidance for tracking, reviewing, and continuously improving them.
The article presents an interview with Tubi Tech Leads, exploring why many would choose the role again, the unique incentives and difficulties of technical management, the importance of data‑driven culture, cross‑regional collaboration, and current hiring for a Big Data Platform Lead.
The article explains how misleading metrics like “watermelon‑type” KPIs can mask poor system availability, introduces the OKRa framework that adds activities to traditional OKRs, and promotes a nationally certified DevOps engineering program to improve end‑to‑end R&D efficiency.
The article recounts JD’s journey from a small team building an in‑house advertising system that saved billions, through successive PC, mobile, and middle‑platform eras, to current AI‑driven retail innovations, highlighting strategic decisions, architectural challenges, and the importance of aligning technology with business goals.
The article explains what metrics are, why they matter, how they can be classified, the structured process for creating effective R&D metrics, criteria for judging good metrics, and practical methods for tracking, reporting, and periodically reviewing them to ensure continuous improvement.
This document outlines a comprehensive Product/Project R&D Management System V3.0, detailing governance principles, requirement analysis, feasibility studies, design, development, testing, release, operation, documentation, cost control, and intellectual property management to ensure disciplined, high‑quality software delivery.
This article presents a comprehensive guide on project control from a QA perspective, covering definitions, key concepts, prerequisites, detailed pre‑test, testing, and post‑release processes, practical scenario tables, and concluding insights to improve testing efficiency and risk management.
This article outlines how technical managers and developers can become effective problem solvers and reliable communicators by understanding problem types, applying a structured resolution methodology, and mastering clear information transfer while respecting privacy and security.
This article reviews JD.com’s automation testing framework, explores how Conway’s Law and organizational culture affect software quality, presents a coupon‑system redesign case, and offers practical guidance on metrics, team cohesion, and probabilistic effort estimation for high‑quality delivery.
This article explains what a team is, outlines its dynamic open‑system nature, presents the PCP‑SCP‑ICP framework, reviews classic team‑development models (especially Tuckman's five stages), describes the leader’s growth path, and offers practical guidance on direction, leadership, roles, systems, communication, relationships, and metrics for assessing team effectiveness.
This guide shares a developer’s personal journey to becoming a CTO, covering the shift from coding to technical operations, building scalable team structures, adopting agile practices, and managing growth in a software startup.
This article explores why and how to measure code quality and development efficiency using code-based metrics, outlines key measurement dimensions, implementation steps, and discusses the benefits and challenges of adopting such quantitative insights for R&D management.
This article outlines how programmers at different career stages—from junior developers to CTOs—should engage with business, details the CTO’s role at each product lifecycle phase, and offers concrete actions for a qualified CTO to help the business thrive.
By defining clear, measurable objectives and key results, aligning them with strategic goals, and continuously testing, prioritizing, and iterating actions, R&D teams can maintain focus, avoid distractions, and translate vision into tangible outcomes through a systematic OKR workflow.
This article describes Anjuke's R&D efficiency measurement framework, detailing its quality and efficiency metrics across project phases, the data collection and processing architecture, visualization dashboards, and analysis methods used to monitor and improve development productivity, reliability, and continuous delivery.
This article compares the realities of staying on a technical track versus moving into management, outlining the ideal and actual daily routines of senior engineers and team leaders, the challenges of career progression, and offers guidance on choosing the path that best fits one’s goals.
This article explores horizontal management—coordinating with developers, designers, and product staff—through four concrete stories, highlighting communication pitfalls, bug‑tracking challenges, and practical steps to improve cross‑functional teamwork and project quality.
The article shares the author’s years of architecture experience at Alipay, arguing that growth into a true architect is a cognitive upgrade, explains what architectural ability really means, illustrates it with a multithreading interview example, and presents systematic thinking methods and practical steps for building architectural competence.
This article explains what architect‑to‑PM transformation means, outlines its characteristic signs and harmful impacts on projects, organizations, and individuals, and offers practical organizational, personal, and cultural measures—including automation pipelines—to keep architects focused on real technical work.
The article explains what a software architect does, outlines four developmental stages—from entry to team collaboration—emphasizes continuous learning, and promotes the 2023 GIAC Global Internet Architecture Conference covering topics like AIGC, cloud native, and digital transformation.
This article outlines comprehensive code review guidelines, covering principles, optimal timing, scope of evaluation, detailed review criteria such as functionality, complexity, testing, naming, documentation, and offers strategies for handling conflicts and maintaining long‑term code quality within development teams.
The article provides a comprehensive overview of the Chief Technology Officer role, covering its definition, required skills, responsibilities, differences from CIO, impact of company size, career path, compensation, and emerging trends in technology leadership.
The article examines the circumstances under which a Scrum team might outgrow the framework, discussing the Stacey matrix, evolution of team maturity, key indicators of diminishing Scrum value, and concluding that teams should abandon Scrum when it no longer serves its risk‑reduction and product‑discovery purpose.
The article explores a new technical ecosystem and delivery model that lets both technical and non‑technical roles participate safely and efficiently in software development, addressing common bottlenecks, ISV integration concerns, and security challenges through zero‑code, plugin, and metadata‑driven solutions.
The article argues that every Scrum event—daily stand‑up, sprint planning, sprint review, and sprint retrospective—is essential for transparency, inspection, and adaptation, making it incorrect to label any single event as the most important.
The article explains why enterprises establish distributed R&D centers—tapping talent, covering markets, cutting costs, and leveraging policies—then details the communication, coordination, and supervision challenges they create, and finally offers three design patterns plus six practical guidelines to mitigate those issues.
In his Spark Award address, Huawei’s founder Ren Zhengfei outlined the company’s R&D investment, the role of mathematics and AI, strategies for university collaboration, talent cultivation, open platforms, and the balance between scientific curiosity and practical technology development.
This article explains the essence of personal growth, outlines a systematic approach to enhance cognition, redesign one's knowledge framework, and create actionable development plans that align individual value creation with team and organizational goals for software engineers and other R&D staff.
The article shares a senior engineer’s reflections on technical architecture at Alibaba, covering top‑level design, physical and application architecture, the evolving role of architects, essential problem‑solving skills, the need for a global perspective, broad technical breadth, continuous learning, and how these insights shape effective R&D management.
This article details how Industrial and Commercial Bank of China’s software development center implements a DevOps‑driven, unified R&D management platform to streamline agile processes, enhance collaboration, automate continuous delivery, enforce quality gates, and support the nation’s digital‑economy strategy.
This article shares the practical methods a R&D team used to create a strong organizational atmosphere, align responsibilities, empower members, and drive performance through OKR, offering concrete steps, case studies, and actionable insights for sustainable growth.
This article examines two common organizational models—vertical and hierarchical division—detailing their structures, operating modes, advantages, drawbacks, and how they influence employee roles, career paths, and overall company performance in the IT industry.
The article recounts a former programmer’s experience of being sued years after leaving a company for alleged bugs in her legacy code, explores the legal and ethical debate over whether developers bear lifelong responsibility for the software they write, and presents diverse viewpoints from the tech community.
The article explains that successful OKR implementation relies on a dual‑wheel drive—cultivating a positive atmosphere and delivering strong performance—so that each reinforces the other, and outlines how managers can foster this balance through trust, fair evaluation, empowerment, and shifting from tactical to strategic mindsets.
MINOS, a low‑code configuration platform for NetEase Yanxuan, translates Apollo’s technical data model into business‑friendly visual forms, lets developers and product users create and approve configurations online, cuts manual R&D effort from minutes to seconds, and has already produced over 4,000 forms across multiple lines.
The author shares a candid account of a year‑and‑a‑half of software development work at a Chinese aerospace institute, describing the modest salary, campus‑like benefits, periods of relaxed development, and the intense, round‑the‑clock pressure of model‑driven projects, to help job‑seekers weigh the trade‑offs of a career in the space sector.
This guide outlines how to create a comprehensive performance assessment framework for technical teams, covering assessment cycles, scoring formulas, KPI and cultural weightings, implementation steps, and the integration of Individual Development Plans to drive both results and personal growth.
The article explains what cross‑functional (non‑functional) requirements are, illustrates common scenarios where they cause system failures, outlines the perspectives of different teams in identifying them, and advises Tech Leads on how to proactively address these requirements while noting an upcoming DevOps hackathon.
This article analyzes common team collaboration challenges, maps them to Patrick Lencioni's five dysfunctions, and presents concrete agile practices—such as welcome/farewell rituals, life‑journey sharing, pair metrics, speedback, and rotating on‑call duties—to build trust, encourage healthy conflict, increase engagement, avoid responsibility avoidance, and focus on results, ultimately fostering a high‑performing, self‑organizing team culture.
The article examines common pitfalls when introducing performance metrics in software development teams, offering five key considerations—metric selection, implementation cost, proper usage, clear value, and team consensus—to ensure metrics drive improvement without adding unnecessary burden.
In business‑driven companies, developers must prioritize understanding the business, foster cross‑team collaboration, and broaden their perspective beyond pure coding, because technical prowess alone is insufficient for survival, growth, and career advancement.
The article reflects on frequent mistakes observed during agile coach hiring—such as weak fundamentals, misaligned positioning, neglect of continuous learning, underestimation of transformation challenges, and unrealistic expectations—offering practical insights on building trust, applying coaching techniques wisely, and navigating real‑world agile adoption.
On December 26, 2022, China Information and Communication Research Institute announced that China Merchants Securities' TianGong R&D Management Platform earned top-level evaluations in both the DevOps system and tool standards, highlighting how its integrated pipeline, CI/CD, and digital transformation initiatives boosted efficiency, quality, and competitiveness.
China Information & Communication Research Institute’s recent DevOps assessment highlighted that China Merchants Securities’ TianGong R&D Management Platform earned excellent ratings in both pipeline and build‑integration modules, showcasing how standardized tools and end‑to‑end workflows can dramatically boost development efficiency, quality, and digital transformation in the financial sector.
This article examines how fragmented metrics and local optimizations can harm overall software quality, discussing the bug‑vs‑feature debate, various measurement approaches, and the importance of viewing quality as a collective team capability rather than an individual or departmental responsibility.
This article explains why midsize tech teams often struggle with outdated infrastructure, outlines a ROI‑driven planning framework, presents real‑world case studies of single‑point breakthroughs and team mergers, and offers a step‑by‑step methodology for systematic technology upgrades and sustainable growth.
This article explains how technical professionals transitioning to management can apply quantitative analysis and systematic measurement to optimize both software system performance—illustrated by an image‑processing pipeline case study—and organizational workflows, highlighting DevOps bottlenecks, resource utilization, and the importance of holistic process improvement.
In this interview, NetEase Cloud Commerce CTO Yin Jingcheng shares his 14‑year journey, stages of technical leadership, practical advice for new managers, strategies for balancing coding and management, and actionable guidance on fostering efficient, innovative R&D teams across business cycles.
This article shares a practical guide on establishing a feedback culture in agile teams, explaining the background, benefits for both team and individuals, step‑by‑step speed‑feedback procedures, common challenges, and actionable tips for giving and receiving constructive feedback.
This article outlines Ctrip's hotel R&D team's systematic approach to boosting development efficiency through OKR alignment, MVP-driven value delivery, agile practice upgrades, and DevOps automation, detailing challenges, solutions, measurement metrics, and continuous improvement strategies.
To cope with the multi‑stage, feature‑rich and rapidly iterated NetEase News recommendation pipeline, the QA team introduced detailed stage logging, controllable recall and user‑profile injection, configurable filters, forced‑push mechanisms, an integrated performance‑testing platform, automated case configuration, centralized requirement tracking, and self‑test tools, dramatically boosting testing quality and efficiency while outlining future automation goals.
The article analyzes why team members resist agile transformation, classifies them into four roles based on perceived benefits and impact, and proposes a phased, benefit‑focused implementation strategy to increase acceptance and reduce opposition.
The article analyzes why software development teams often see productivity drop as headcount grows, explains communication‑cost theory, introduces a 5S model covering design, development, testing, management and support stages, and recommends enterprise architecture and domain‑driven design to curb complexity and boost delivery speed.
The 2022 GOITI IT Technology Leadership Awards highlighted Zhongyuan Bank’s EPG Process Improvement Team, whose dual‑mode, multi‑speed delivery framework, online management platform, intelligent performance metrics, and data‑driven improvement loop have transformed the bank’s R&D efficiency, accelerated product cycles, and earned multiple industry certifications.
The article examines the challenges of quantifying software R&D productivity, critiques traditional metrics, introduces a set of balanced key performance indicators, and proposes a composite efficiency index (CEI) that combines delivery throughput, deployment frequency, success rate, cycle time, stability, and debt backlog.
The STREET framework outlines a structured process—Scope, Track, Rank, Evaluate, Evangelize, and Transfer—to guide organizations in assessing, adopting, and deploying emerging technologies in alignment with strategic goals and risk tolerance.
The article analyzes a Chinese labor dispute where a machine‑vision algorithm engineer was dismissed for producing only a few hundred lines of code, detailing the employment contract, performance assessments, evidentiary materials, the court’s finding of illegal termination, and the compensation awarded.
This article uses vivid analogies—professional craftsman, orchestra conductor, and film director—to explain Alibaba's technical job level system (P5‑P10), outlining core responsibilities, skill expectations, and the differences between each tier for developers, testers, and ops professionals.
The article explains why a progressive, incremental approach to business architecture—balancing clear primary requirements with flexible handling of secondary and emergent features—helps large‑scale website projects avoid the pitfalls of rigid waterfall planning and enables smoother versioned development.
The article explains the four‑hold principles from Continuous Delivery 2.0—doing less, continuously decomposing work, constantly gathering feedback, and pursuing ongoing improvement—and shows how applying them can eliminate late‑night release cycles, improve DevOps feedback loops, and strengthen R&D management in software projects.
The article argues that a CTO or technical VP must possess deep technical expertise to evaluate quality, guide architecture, earn team respect, inspire innovation, and attract top engineers, illustrating these points with real‑world examples from Dropbox and Facebook.
This article outlines six key software architecture principles—reuse before build, cloud‑ready design, scalability, complexity reduction, API‑first approach, and frequent small releases—to help organizations make strategic technical decisions and avoid common pitfalls.
This article explores why traditional offline stores still matter after COVID‑19, outlines practical standards for store design—including better aesthetics, cost‑effective materials, and easy execution—and offers management tactics such as approval workflows, supportive tools, priority weighting, and experience‑capture to boost efficiency and brand influence.
This article compares the traditional Waterfall development model with the Agile Scrum approach, outlining each method's strengths and weaknesses, describing Scrum roles and workflow, and offering practical insights on when and how to apply either model in software projects.
The article outlines a five‑stage technical career roadmap—from junior engineer to CTO—describes the three‑tier technical capability model (implementation, architecture, leadership), and offers practical advice for professionals at each level to balance technical work and management responsibilities.
The article predicts smartphones will dominate traffic for the next three years, argues that cross‑device frameworks like ReactNative, Weex and Flutter are essential, and proposes a streamlined R&D model at Xianyu with full‑stack mobile engineers and infrastructure engineers supported by a unified container, programming plane, workflow, and the high‑performance, W3C‑compliant KUN rendering engine to boost iteration speed, consistency, and talent efficiency.
This article outlines comprehensive guidelines for keeping customers happy, managing projects, designing robust APIs, conducting thorough code reviews, shaping strategic direction, ensuring observability, and fostering research, all aimed at building resilient and high‑performing engineering teams.
This article recounts a real-world incident where a junior engineer mistakenly uploaded production data to a pre‑release environment, analyzes the root causes, outlines concrete process improvements, and highlights broader lessons on risk‑aware development and the importance of holistic business‑logic security.
The article outlines comprehensive quality‑assurance approaches for technical improvement projects—such as large‑scale refactoring, architecture upgrades, and migrations—by emphasizing risk‑driven planning, automated testing, business‑centric reviews, non‑functional requirement validation, and continuous knowledge sharing.
This article outlines a comprehensive R&D management framework—covering background, pain points, goals, and a five‑dimensional approach (Dao, Fa, Shu, Qi, Shi)—to help technical leaders design culture, principles, processes, standards, tools, and incentives that enable high‑performing teams of dozens to thousands of engineers.
The article explains that most software products only need sufficient quality rather than high quality, outlines how to identify software quality requirements, discusses the impact of team health on quality outcomes, and offers guidance on when to invest or hold back on further improvements.
This article outlines how technical leaders can construct a comprehensive R&D management system for teams of hundreds to thousands by addressing cultural foundations, process standardization, tool integration, talent lifecycle, and strategic momentum, ultimately enabling focused, high‑performing development organizations.
This article outlines how technical leaders can construct a systematic R&D management framework—covering background, pain points, goals, and the five dimensions of Dao, Fa, Shu, Qi, and Shi—to foster culture, standardize processes, develop talent, leverage tools, and align with strategic trends for high‑performing engineering teams.
The article outlines how senior architects can construct a systematic R&D management framework—covering background, pain points, goals, and five key dimensions of culture, processes, talent, tools, and strategy—to enable large technical teams to stay focused, grow, and deliver high‑quality results efficiently.
The article examines why engineering efficiency has been overlooked amid rapid business growth, describes the emerging infrastructure and tool platform debt that hampers software development, and discusses how R&D management can address these challenges through better tooling, measurement, and strategic investment.
The article explains how R&D managers can boost efficiency by treating team workflows like system performance optimization, using measurement, architectural redesign, and value‑stream analysis to identify bottlenecks and achieve cost‑effective improvements across development, testing, and operations.
The article explains how technical professionals promoted to management can apply quantitative measurement and systematic optimization—illustrated with an image‑recognition service case and a DevOps defect‑resolution workflow—to improve resource utilization, reduce bottlenecks, and align R&D processes with lean, value‑stream principles.
The article explains how technical leaders can apply quantitative analysis and systematic measurement to optimize both software system performance and organizational workflows, using a picture‑recognition service example and a real‑world DevOps incident to illustrate the need for end‑to‑end process mapping, bottleneck identification, and continuous improvement.
The article reflects on a dozen years of software development experience to propose three evolving definitions of a software architect, classify various architect roles, and compare centralized versus collaborative work styles, highlighting why the term is often misused in the industry.
The article analyzes why big and medium‑sized companies often reinvent existing tools—due to unsatisfactory open‑source options, desire for technical prestige, low priority of requests, and skill development—and offers organizational strategies to evaluate, coordinate, and incentivize such efforts responsibly.
The article outlines systematic questioning strategies for judges in corporate promotion defenses, detailing how to clarify definitions, probe processes, assess difficulty, evaluate big‑picture thinking, explore methodology, and link technical work to business value, thereby ensuring fair and insightful evaluations.
This article presents thirty practical software‑architecture principles—from keeping designs simple and avoiding unnecessary features to mastering concurrency, distributed systems, and user experience—providing a comprehensive guide that helps architects make informed, ROI‑driven decisions while fostering scalable, maintainable solutions.
The article outlines comprehensive quality assurance approaches for technical improvement projects, highlighting risk-driven processes, automated testing, business perspective integration, and the importance of addressing non‑functional requirements to ensure stable, reliable system upgrades.
The article reflects on a dozen years of software development experience to propose three evolving definitions of a software architect, examines why the term is often misused, categorises different architect types, and compares centralized versus connective work styles for effective R&D management.
The article analyzes why major Chinese internet firms are cutting staff while aggressively recruiting, highlighting the industry's asset-light, talent‑heavy nature, the need for rapid product experimentation, middle‑manager redundancy, and the influx of fresh graduates, and offers perspectives on navigating these contradictory trends.
The article shows how technical leaders promoted to management can apply quantitative analysis and systematic measurement—illustrated through an image‑recognition service optimization—to identify bottlenecks, redesign processes, and boost overall team efficiency in software development.
