The article argues that relentless pursuit of efficiency—seeking the shortest path—can stifle innovation, illustrating how purposeful waste, redundant resources, and flexible timing at companies like ByteDance, Tencent, and Huawei foster breakthrough ideas while balancing the need for eventual optimization.
This guide outlines a four‑step framework for taking over a new technical team, detailing six key tables for people, talent pipelines, development plans, responsibilities, and project mapping, and explains how to align goals, communicate effectively, and track progress with OKR/KPI mechanisms.
This guide outlines how senior engineers moving from large tech firms to smaller startups can adapt quickly by cultivating the right mindset, pacing their onboarding, integrating with teams, addressing technical and organizational challenges, and ultimately mastering the new environment through humility, decisive action, and systematic team development.
This article details China Merchants Bank’s multi‑year, value‑driven lean transformation—describing the three major challenges of large‑scale digital change, the 3‑1‑2 framework (three steps, one integrated system, two key tools), the 4+1 management model, the 6+2 methodology, and the practical outcomes achieved through the LeanStar platform and a dedicated consulting team.
The article argues that performance evaluations often demoralize employees because they focus on individuals rather than objectives, advocates shifting scores to projects, products, or teams, critiques the misuse of KPI and OKR, and offers personal reflections on finding growth beyond corporate metrics.
The article shares a senior engineer’s practical experience on combining open‑source and self‑developed components, analysing their advantages, lifecycle stages, and concrete strategies—including problem definition, selection, source‑code control, and ten actionable tips—to help teams balance cost, innovation, and stability.
Technical leaders scaling teams beyond a hundred members can adopt a systematic R&D management framework—covering culture, processes, talent, tools, and strategic positioning—to align goals, boost efficiency, and sustain growth across fast‑moving businesses.
This article examines why many developers struggle with low productivity, revisits Brooks' 10x programmer insight, and introduces a simple three‑question thinking framework plus five practical principles to help programmers clarify goals, assess current status, and plan effective execution paths.
This article shares practical insights on balancing open‑source and self‑developed components in core platform projects, covering advantages, lifecycle stages, performance profiling, code‑base management, and engineering practices that help teams achieve sustainable growth and innovation.
The article explains why software development efficiency has become a buzzword, outlines four underlying reasons, presents a comprehensive set of measurable indicators across planning, feedback, team transformation, decision support and engineering capability, and offers practical guidance on selecting and evolving metrics for different project types.
This article outlines the comprehensive architecture and key points for building digital R&D management capabilities in financial organizations, reviewing historical challenges, identifying four major pain points, proposing an overall framework, detailing twelve essential capabilities, and offering principles for effective implementation.
The article explains the evolving role of the Chief Technology Officer (CTO), detailing their responsibilities, required skills, differences from CIOs, impact of company size, career trajectory, compensation, and future trends in technology leadership within modern enterprises.
In this interview, Qunar's Technology Committee chair Wang Zhimeng shares how the company built its technology brand over the past two years, detailing the challenges, strategies, achievements, and future plans for fostering a strong technical community and enhancing talent attraction.
In a satirical yet insightful piece, the author outlines thirteen deliberately harmful practices a leader can employ to sabotage a core employee, illustrating how misguided management decisions can erode talent, morale, and organizational health over time.
The article examines how agile testing shifts quality ownership from individuals to the whole team, outlines the responsibility process model—from denial to responsibility—and proposes three keys (intention, awareness, confrontation) to cultivate a genuine sense of responsibility within development teams.
This article examines why IT talent is the most expensive resource, analyzes environmental, temporal, and human factors, and proposes a structured change management framework—including clear methodology, strong leadership support, and iterative improvement principles—to optimize IT resource allocation and reduce costs.
This article shares a step‑by‑step case study of how an agile coach transformed a team anniversary celebration into a focused workshop that sparked open dialogue, strengthened collaboration, and delivered measurable improvements in team spirit and performance.
The article outlines how R&D organizations evolve from functional to cross‑functional Scrum teams using a 3‑3‑5‑5 framework, physical and electronic Kanban (Jira with plugins), defined domain, project and story owners, and data‑driven metrics to monitor effectiveness, align product and research, and continuously improve value delivery across design, implementation and operation.
This article outlines a comprehensive R&D management framework—covering culture, processes, people, tools, and strategy—to help technical leaders scale teams beyond a hundred members, align goals, improve efficiency, and sustain high‑performance delivery while fostering growth and motivation.
The article outlines a systematic R&D management framework that addresses the challenges of scaling technical teams, defines five core dimensions—culture, processes, talent, tools, and strategy—and provides concrete practices for building culture, standards, recruitment, organization, growth, incentives, performance, and tooling to enable high‑performing, goal‑driven engineering organizations.
This guide outlines the mindset, rhythm, and concrete actions senior technology managers need to adopt when transitioning from large enterprises to smaller companies, covering humility, rapid integration, whole‑hearted work attitude, strategic pacing, team building, and systematic process implementation.
The Rust language audit team resigned en masse on November 22, protesting the core team's lack of accountability, prompting community debate on open‑source governance and leading to four concrete recommendations and the appointment of a temporary replacement group.
The article shares ten practical principles—owner mindset, time awareness, start with the end, closed‑loop thinking, respect for standards, avoiding repeated mistakes, design first, balancing output and capacity, asking good questions, and maintaining an empty‑cup mindset—to help engineers improve personal growth, team efficiency, and overall work quality.
The article explains why Scrum teams must be cross‑functional, describes the problems caused by missing skills or external dependencies, and offers practical ways to develop such teams through internal training, contracts, small stable groups, and a paper‑airplane game to illustrate agile principles.
This article offers nine practical recommendations for researchers and technologists launching startups, covering partner selection, strategic HR leadership, professional legal and financial planning, continuous personal growth, cross‑industry networking, prioritizing IP over publications, adopting market‑driven thinking, engaging with government policies, and embracing human‑centric management.
The article reviews New Oriental’s AI research institute journey, analyzing AI development trends, challenges, performance metrics, organizational structure, cost‑reduction strategies, and product innovations in education, offering practical insights for AI R&D management and enterprise AI deployment.
This article details how an agile coach designed and ran a soul‑stirring anniversary workshop for a development team, covering pre‑work interviews, focused strategy, data‑driven discussions, staged questioning, contingency planning, and the resulting feedback that boosted team cohesion and performance.
The article defines delivery capability as the ability to provide usable, complete results, explains why thorough delivery matters, and outlines concrete delivery standards for backend, frontend/mobile, and QA roles to achieve high‑quality, end‑to‑end software outcomes.
Most business development engineers cling to a narrow self‑identity focused on coding, overlooking the broader responsibilities of driving customer digitalization; this article examines common mindset traps, their origins, and offers a structured framework for shifting perception, expanding roles, and evolving into a technical leader who balances both technology and business.
This article shares ten practical principles—ranging from ownership and time management to continuous learning and balanced output—that help engineers avoid common pitfalls, improve team efficiency, and foster personal and professional growth.
This article explains why a strong engineering culture is essential for software delivery, quality, and employee satisfaction, and outlines three practical steps—defining core values, implementing supporting mechanisms, and living the values—to create and sustain such a culture within a company.
This article shares a real-world low-code implementation story, analyzes where low-code excels and fails, and offers five practical strategies for technical leaders to navigate efficiency gains, workforce impacts, and future-proof their development teams.
A software engineering manager shares a candid account of handling a team member’s resignation, describing the warning signs, one‑on‑one discussion, transition planning, personal reflections on communication and support, and the broader lesson of fostering graceful exits in a fluid tech industry.
In this interview, Zhou Xiaosi shares his seven‑year journey at QingCloud, the challenges of launching KubeSphere, his product and R&D management philosophy, and why hybrid‑cloud and cloud‑native strategies are essential for Chinese software to become globally competitive.
The article chronicles a senior engineer’s rise from a PHP/MySQL developer to CTO of Ant Group and Alibaba, illustrating how strategic shifts—from Java EE migration and cloud‑native, OceanBase‑based architectures to “going‑IOE” and massive payment scaling—paralleled business growth, while sharing six leadership principles, risk‑management lessons, and advice for cultivating future CTOs.
This article describes how the Auto Home Dealer business unit transformed its software quality process over three years by piloting, scaling, and institutionalizing testing practices, addressing role‑specific challenges, introducing automation, and continuously measuring impact to achieve faster, more reliable releases.
The article argues that over the past decade China's rapid, short‑term development model has created a serious talent gap in software architecture for B2B and industrial internet sectors, limiting the country's core competitiveness despite flourishing consumer‑facing tech companies.
This article shares practical collaboration strategies through real‑world cases, explaining why framing proposals around others' benefits, identifying the right partners, and aligning mutual goals can turn complex technical challenges—like slow‑SQL governance and barcode‑scale integration—into successful joint projects.
This article presents 30 widely‑accepted software architecture principles—grouped into basics, feature selection, server design, distributed systems, user experience, and challenges—to help architects act as gardeners who shape, refine, and sustain robust, maintainable systems.
The article recounts LinkedIn’s rapid 2011 growth, the mounting technical debt that forced a two‑month feature freeze, and how the InVersion project rebuilt the development platform, offering lessons on disciplined debt repayment and engineering process improvement.
This article outlines a four‑stage career roadmap for technology professionals, guiding them from the first years after graduation through independent contribution, team leadership, and finally strategic innovation, with practical advice on learning, problem‑solving, mentorship, and industry foresight.
This article examines how competition and ecosystem dynamics influence digital transformation, highlighting internal versus external rivalry, the shift from blind adoption to strategic value, and the role of technology integration in creating flexible, resource‑rich environments that drive sustainable business growth.
This interview explores the six‑year evolution of the dubbogo project, the motivations, challenges, and biggest contributions of PMC member Wongoo, and his vision for the future of this high‑quality Go implementation of the Dubbo RPC framework.
This article outlines a comprehensive approach for technology leaders to create a fast‑responding, high‑efficiency engineering team by integrating business, technology, monitoring, operations, and management practices, detailing goals, frameworks, and measurable outcomes.
The article critiques traditional defect‑per‑KLOC and test‑case failure metrics, explains why they are misleading, and proposes a system‑thinking approach to quality efficiency that focuses on ROI, trend analysis, and building a high‑response, well‑structured development ecosystem.
The article explains how R&D efficiency can be measured only externally, outlines the fast verification loop concept, and details four core principles—build quality in, eliminate waiting, eliminate trivial work, and monitor everything—to improve software delivery speed and quality.
The article explores why many programmers feel lost, explains the business‑technology‑software value chain, and argues that adopting a value‑driven architectural mindset helps align learning and work with real business impact, improving both personal fulfillment and organizational outcomes.
This article uncovers the universal patterns governing business lifecycles, technology evolution, and organizational dynamics, offering practical strategies for technical leaders to anticipate challenges, align teams, and break or leverage these laws to drive sustainable growth and innovation.
This article explores how the concept of "flow" can transform software development by addressing distractions, meetings, and mental inertia, and offers practical strategies such as scheduling focused coding time, improving documentation, running efficient meetings, and leveraging data‑driven tools like Time Master to enhance productivity and work‑life balance.
By adapting growth‑hacking concepts such as north‑star metrics, conversion funnels, and A/B testing to the software development lifecycle, this article proposes a data‑driven “efficiency hacker” model that visualizes demand delivery paths, classifies tasks with the RIW framework, and guides teams toward faster, more transparent project outcomes.
This article examines why software outsourcing firms are often unpopular, outlines their definitions and stereotypes, compares project‑based and personnel‑based outsourcing, offers practical tips for identifying such companies during recruitment, and explains why many professionals prefer product‑oriented firms.
This article presents Autohome's Cloud Platform (Home Cloud) technical debt governance framework, defining ideal technical states, outlining five systematic steps—from factor collection to project execution—and sharing practical outcomes that have enhanced the competitiveness of its applications and development teams.
This article shares a former programmer’s journey to technical leadership, outlining essential competencies, the shift in mindset from individual contributor to manager, practical ways to boost team efficiency and cohesion, communication and emotion‑control techniques, self‑growth strategies, and energy‑management tips for sustainable success.
The article explains the distinction between software outsourcing and product companies, examines common stereotypes, outlines the characteristics of project outsourcing, personnel outsourcing, and product-oriented firms, and provides practical tips for recognizing outsourcing firms during recruitment and interviews.
This guide explains the concept, purpose, and four types of retrospectives, then details a complete workflow—including pre‑meeting preparation, structured discussion, and post‑meeting follow‑up—while introducing practical tools such as the Six Thinking Hats, World Café, Q10, goal‑tree, fishbone diagram, and benefit‑effort matrix to drive continuous improvement.
The article chronicles Liang Rubo’s journey from a university roommate of Zhang Yiming to ByteDance’s trusted successor, highlighting his technical background, diverse responsibilities, and the organizational challenges he must navigate as the company expands globally.
This article explains the essence of software architecture, outlines its main components, classifies various architecture layers such as business, application, code, and technical architecture, discusses evolution stages, measurement criteria, common pitfalls, and provides a comprehensive knowledge framework for architects.
The article surveys five major software testing organization models—centralized, decentralized, hybrid, third‑party, and “no‑testing”—explaining their evolution, characteristics, advantages, and challenges, and discusses how agile practices and business needs drive the shift toward integrated or outsourced testing structures.
The article follows three Didi Ride‑Hailing engineers who joined in 2016 as fresh PhDs, detailing how they leveraged machine‑learning, dynamic dispatch, and product‑line automation to rise from junior developers to technical leaders, highlighting the blend of hard coding, soft communication, rapid‑learning culture, and the team’s current senior‑role hiring drive.
This comprehensive guide explains why software architects are needed, defines key architectural concepts, outlines the architect's duties across the software lifecycle, presents a 12‑point capability model, and offers practical methods for cultivating and advancing in the architect role.
This guide presents a mentor‑driven onboarding framework that helps new R&D engineers quickly overcome language and project challenges by focusing on essential programming concepts, fast‑learning tags, experiment‑driven and test‑driven development, and clear project hand‑off procedures, ultimately boosting team delivery speed.
This article explores how algorithm engineers and researchers can navigate their career paths by understanding company organizational structures, talent models, and a series of reflective questions about specialization, management, and balancing research with engineering work.
The article outlines CI/CD best practices for ToB platforms, detailing standardized branch and pipeline conventions, automated testing with Jest, versioning strategies, frontend‑backend contract design, and tools like YAPI to ensure reliable, fast, and decoupled deployments across numerous coupled systems.
By applying the DRY principle, the team abstracted audit requirements into a micro‑core plugin architecture, built a two‑week MVP for Xianyu’s community moderation, and demonstrated how systematic research, reusable patterns, and incremental evolution prevent duplicated effort and create a scalable, maintainable audit system.
This article describes how Baidu's intelligent delivery team tackled challenges of multi‑team, multi‑project web development by standardizing R&D processes, leveraging cloud‑native architectures, automating environment setup, and applying data‑driven testing to achieve faster, higher‑quality continuous integration and delivery.
iQIYI CTO Liu Wenfeng explains that virtual production—combining LED walls, XR, AI, big data, and cloud‑based game‑engine technology—is reshaping entertainment by delivering realistic, real‑time sets, streamlining workflows, fostering creator‑developer collaboration, and paving the way for an interactive Metaverse beyond traditional green‑screen methods.
Drawing from four years of experience as a technical team leader at Alibaba, the article shares practical insights on recruitment, goal definition, effective communication, fostering a strong engineering culture, and personal reflections, offering guidance for managers seeking to build high‑performing, innovative development teams.
The article explores why enterprises must continuously innovate, outlines the challenges of cross‑industry disruption, digital transformation, and VUCA environments, and presents JD.com’s lean innovation process, S‑curve growth model, three‑horizon strategy, and concrete internal innovation cases to drive sustainable growth.
This article explores how physical design analysis—monitoring file‑system changes, commit frequency, and module size—can reveal the stability, coupling, and learning cost of a large‑scale software project, using Redis as a concrete case study and the open‑source tool Coco for measurement.
This article reviews key insights from the book “How Google Tests Software”, highlighting Google’s view that quality stems from integrated development and testing, describing the distinct roles of SWE, SET, and TE, and comparing these practices with typical domestic software testing structures.
The article examines Netflix’s distinctive corporate culture—emphasizing high talent density, candid communication, minimal controls, market‑leading compensation, and radical transparency—to illustrate how these principles drive innovation, employee engagement, and sustained business success.
The article explains the concept of innovation networks, outlines four key roles—Inventor, Transformer, Financier, and Broker—describes the surrounding ecosystem, and provides practical guidance on aligning values, understanding organizational capabilities, and mapping metrics to improve network performance.
This article details how KuJiaLe's internal "Afu Workshop" used agile coaching steps—assessment, training, calibration, creative retrospectives, and continuous feedback—to dramatically improve sprint completion rates, velocity, and team satisfaction across two product squads.
This article chronicles Kuaishou’s ten‑year journey from a humble GIF‑making app created by Cheng Yixiao, through its partnership with Su Hua, strategic pivots, IPO success and subsequent controversies, illustrating how focused product design and relentless R&D management built China’s premier short‑video platform.
The article examines Huawei's 30‑year journey of sustained growth, emphasizing relentless struggle, open human‑resource practices, self‑criticism, and a culture of continuous learning as key strategies to reduce organizational entropy and maintain vitality.
The article outlines three developmental stages for engineers—from merely implementing PRD specifications, to understanding business and selecting appropriate technical solutions, and finally proactively contributing business ideas—while describing practical methods for demand exploration, project initiation, management, and data‑driven iteration within a mobile development context.
Alibaba’s senior leader Zhang Yong admits the company’s middle‑platform has become too slow, announcing a shift toward a thinner, more agile architecture and explaining how this change reflects the limits of combinatorial innovation versus disruptive innovation in large enterprises.
The article examines why traditional middle‑platform models struggle with disruptive innovation and explains how companies like Tencent and Alibaba use competitive “horse‑race” mechanisms and a “thin middle platform” approach to foster breakthrough products such as WeChat and DingTalk.
This article outlines common disruptive behaviors of "pig teammates" in project teams and provides concrete strategies—clarifying responsibilities, reducing conflicts, improving communication, confronting stubborn members, and motivating lax contributors—to help project managers maintain progress and team cohesion.
The article reviews recent leadership changes in Alibaba's middle‑platform division, recounts the history of the 2015 "big middle platform, small front‑end" strategy, analyzes why the initiative has struggled, and reflects on the broader implications for enterprise architecture and R&D management.
This case study details how Zhenkunhang’s product technology center adopted the Scaled Agile Framework (SAFe) in 2020, reorganizing teams, redefining requirements, improving quality, deploying new project‑management tools, and fostering a lean‑agile mindset to accelerate delivery and enhance product value.
The PODE (Product + OKR + DevOps + Empower) framework, created by China Unicom’s Operations and Scheduling Center, restructures product teams, aligns objectives with measurable results, adopts DevOps practices, and empowers staff, dramatically improving collaboration, efficiency, and product quality across distributed teams.
The article chronicles how 5G and AI are reshaping global manufacturing, how US sanctions crippled Huawei’s chip supply, and how visionary leader Zhang Rujing built China’s semiconductor industry from scratch, turning SMIC into a lifeline for domestic chip production.
The article explains how Grab’s principal engineers lead large technical families, own complex micro‑service systems, drive architectural quality, manage cross‑team projects, mentor engineers, and balance technical and business impact, offering practical guidance for senior engineering career growth.
The article explains how Azure DevOps and Azure DevOps Server adopted agile principles, detailing team organization, cultural shifts, planning hierarchies, defect‑limit practices, and new health‑preserving methods that together improve collaboration, transparency, and delivery cadence.
A senior IT leader’s frustration with a middle‑platform project reveals how vague goals, insufficient budgeting, lack of real business scenarios, and misaligned expectations between management and consultants can doom enterprise transformation initiatives, offering hard‑earned lessons for future R&D managers.
The article analyzes how digital transformation reshapes corporate growth from traditional organic methods to inorganic, technology‑driven strategies—such as tech‑driven growth, business‑model innovation, and domain expansion—and introduces external levers like range M&A, corporate venture capital, and ecosystem building that together permanently reorganize the growth landscape.
The eight‑dimension low‑code capability measurement model evaluates platforms across business scenario breadth, user‑group reach, technical completeness, material inclusiveness, product richness, production‑chain coverage, collaboration efficiency, and intelligence, providing a traceable framework to assess maturity and guide future evolution.
This article explains how 58.com’s UX design team created a unified design system—covering standards, core principles, shared assets, and specialized tools—to streamline cross‑business collaboration, reduce redundant work, and accelerate product development across its massive classified‑services platform.
An independent developer's X browser used an open‑source ad‑blocking rule that blocked Youku pre‑roll ads, prompting a 1 million‑yuan lawsuit and highlighting the legal risks of using third‑party plugins without professional counsel, proper disclosure, or proactive settlement efforts.
This article explains how systematic defect analysis can transform bugs into valuable learning opportunities, outlines five practical practices—including timely summaries, pair analysis, negative‑list filtering, actionable outcomes, and team‑wide learning mechanisms—and shows how these steps reduce future defects while strengthening R&D capabilities.
This article outlines a step‑by‑step career roadmap for developers who aspire to become software architects, covering role definitions, required technical and managerial skills, learning pathways such as OOP, design patterns and refactoring, and practical advice for continuous self‑improvement.
The article outlines the essential competencies—technical mastery, business understanding, design foresight, depth and breadth of knowledge, communication, and systematic thinking—that a software architect must develop to effectively lead and deliver complex projects within an organization.
This article explains how to conduct thorough requirement analysis, classify and prioritize needs, and translate them into solid software architecture decisions, highlighting demand capture, functional, quality, and constraint considerations, as well as practical steps for prioritization and implementation.
This comprehensive article explains the concept of the mid‑platform (Zhongtai), its origins, classification into business, data, algorithm, technical, R&D, and organizational platforms, examines the challenges it solves, and reviews real‑world implementations by Alibaba, Huawei, NetEase, Baidu, and Tencent, concluding with practical guidance for adopting a suitable platform strategy.
This article examines common pitfalls in code quality, testing, and development efficiency, analyzes their root causes, and proposes concrete, actionable solutions such as performance optimization, stricter coding standards, regular code reviews, improved testing practices, and enhanced team collaboration to boost overall software project success.
This article reviews common industry Git workflows such as Git Flow, GitHub Flow, GitLab Flow, Trunk‑based Flow and Aone Flow, analyzes Bytedance's multi‑environment deployment architecture, and presents concrete single‑, double‑ and triple‑branch practices together with recommendations for effective R&D process management.
This article outlines how a structured Innovation Training Camp empowers designers to break business silos, generate patents and new service concepts, and systematically turn creative ideas into implementable solutions that enhance product experience and drive continuous improvement.
This article offers practical advice for software engineers facing mid‑career challenges, outlining eight actionable principles—from avoiding stagnation and maintaining competitiveness to diversifying income and planning for a transition beyond coding—to help them sustain growth and resilience in a demanding industry.
The article explains Alibaba’s five‑category talent assessment model, illustrates the nine‑box grid method, and provides a step‑by‑step guide for technical teams to conduct talent reviews, align staff with strategic goals, and develop targeted development and succession plans.
