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.
The article argues that the so‑called middle platform is mostly a buzzword used to impress non‑technical stakeholders, explains why traditional enterprises without strong R&D struggle to adopt it, and outlines practical viewpoints on business, data, and technology middle platforms, including the fragmented‑middle‑platform approach.
In this candid post, a former technical director shares a three‑month case study of team mismanagement, detailing four critical mistakes—over‑estimating talent, under‑estimating project difficulty, spreading resources too thin, and neglecting proper management—along with reflective insights and actionable lessons for future leaders.
This article presents a detailed case‑study of how a transaction platform improves overall project quality by formalizing multi‑stage acceptance, introducing a virtual‑city environment for efficient online verification, and continuously operating acceptance metrics to achieve high‑quality, stable releases.
The article explores why seniority alone doesn’t measure a developer’s ability, explains fixed versus growth mindsets, and offers practical strategies—targeted learning, deliberate practice, embracing business development, and cultivating empathy—to sustain continuous professional growth throughout a software engineering career.
This article explains why a quality‑score model was created, reviews industry quality‑measurement practices, describes how key indicators were selected and weighted, outlines the calculation formula, and shares the implementation approach and observed benefits for improving product quality and risk control.
A senior Alibaba front‑end engineer shares personal reflections on thinking methods, communication tactics, execution habits, growth mindset, and promotion experiences, offering practical advice for anyone aiming to advance in a fast‑paced tech environment.
The article introduces the Goudison Theorem, emphasizing that newly promoted technical leaders should avoid overworking themselves, delegate effectively, empower their teams, and focus on sustainable management practices to build high‑performance groups.
This article explains the purpose, types, and practical benefits of maturity models for scaling Agile and DevOps in enterprises, outlining stage‑based and continuous models, design principles, and how they help teams assess current capability, set improvement goals, and continuously enhance delivery efficiency.
The article explains how a lack of structured thinking leads to communication gaps, low business value, and missed promotion opportunities, and it offers a practical framework—including building a central goal, hierarchical decomposition, and tools like SWOT and AHP—to help individuals and teams clarify objectives, prioritize actions, and achieve greater effectiveness.
The article examines why top developers leave, exploring concepts such as the value‑peak curve, the “Dead Sea effect,” boredom, and lack of autonomy, and offers practical vision‑based retention tactics that align with developers’ desires for mastery, purpose, and control.
This article analyzes Youzan’s hybrid organizational model that blends functional teams with Feature Teams, detailing the shortcomings of traditional functional structures, the criteria for adopting Feature Teams, and practical steps for aligning goals, self‑organizing, resource planning, and decision‑making to achieve more agile collaboration.
This article presents 30 practical guidelines for technical leaders, covering team structuring, agile practices, communication, performance tracking, and cultural initiatives to enhance productivity and morale within engineering groups while also warning against common pitfalls and emphasizing the importance of empathy and continuous improvement.
This article examines how DevOps adoption transformed the Agricultural Bank’s enterprise‑level R&D management system, detailing its evolution, the operational and cultural shifts introduced, and practical recommendations for integrating DevOps, agile, and continuous delivery at scale.
In complex, highly specialized organizations, cross‑team collaboration often suffers from misaligned goals and delayed issue detection, but applying OKR with clear alignment, regular reviews, and timely re‑calibration can dramatically improve coordination and reduce hidden losses.
Youzan’s Efficiency Improvement team introduced project‑based management to bring transparency, empower part‑time PMs, and foster self‑organization, then layered Large‑Scale Scrum across component teams, enabling dynamic equilibrium between order and chaos and evolving the R&D organization toward agile, scalable efficiency.
This article chronicles JD's journey of creating a proprietary brand typeface—from the strategic need for visual consistency, through early DIY experiments and scaling challenges, to a professional partnership with Fangzheng, rule refinement, variable‑font prospects, and the broader impact on brand identity.
This article expands on risk management by detailing practical methods for risk identification—such as silent brainstorming and risk breakdown structures—and presenting a combined "1‑2" approach, while also outlining sustainable risk monitoring mechanisms like daily briefs and a case‑library for agile teams.
The article explains the two‑pizza team principle, arguing that keeping development teams small enough to be fed by two pizzas reduces communication overhead, encourages self‑organization and cross‑functional collaboration, and ultimately leads to more sustainable and faster project delivery than expanding large, unwieldy groups.
An innovation network is a refined management approach that aligns four key roles—Inventor, Transformer, Financier, and Broker—within an ecosystem, emphasizing shared values, organizational capabilities, and metric mapping to improve network performance and sustainable value creation.
The article reflects on the recent Matlab ban in China, examines the historical development of Matlab and other long‑standing software, extracts four strategic principles for creating indispensable technology, and urges a shift in mindset toward sustained, practical innovation over quick academic output.
This reflective essay shares a seasoned NetEase engineer's journey and practical advice on technical mastery, stepping out of comfort zones, overcoming career plateaus, planning long‑term growth, fostering respectful teamwork, embracing open mindsets, and developing business‑focused thinking to thrive in modern software development.
This article explores the Monkey Theory—a management framework that defines how tasks (the “monkeys”) should be assigned, fed, or eliminated—to help leaders prevent bottlenecks, empower employees, and boost project delivery through clear delegation, five task‑level classifications, and six practical feeding principles.
This article explains the concept of DevOps, the challenges faced by a multi‑technology development team, and how the RDMS platform integrates CI/CD, Kubernetes, and approval workflows to streamline backend and frontend deployments while improving security, management cost, and operational efficiency.
The article explains why teams should focus on delivering value rather than isolated features, defines the concept of a value stream in software development, outlines its four essential components, and describes how to visualize and improve it through a collaborative DevOps Transform Canvas workshop.
This article describes the design, implementation, and operational strategy of a comprehensive code‑metrics platform that standardizes coding standards, automates quality checks, and drives data‑guided improvements across multiple development teams, ultimately enhancing code reliability, maintainability, and CI/CD flow.
This article presents a structured debate on the effectiveness of positive and negative incentives in team management, featuring expert viewpoints, real‑world case studies, practical Q&A, a concise summary of key takeaways, and recommended reading for leaders seeking to motivate high‑performing teams.
In this detailed interview, former Google quantum hardware lead John Martinis explains his unexpected resignation, recounts his role in achieving quantum supremacy, discusses team dynamics, leadership challenges, future quantum‑computing plans, and offers insight into the broader implications for the field.
The article explains the distinction between part‑time and full‑time software architects, outlines the core responsibilities such as global technical planning, unified methods and standards, robust foundational construction, and practical implementation, and discusses the rights, assessment criteria, and practical ideas for establishing an effective architecture function within large organizations.
This article examines how stable, non‑startup companies can develop their technical teams by addressing recruitment, personnel development, team culture, technology stack decisions, project management practices, and promotion pathways, offering practical insights for effective R&D management.
Beike’s real‑estate platform transitioned from a monolithic application to a service‑oriented, domain‑driven mid‑platform, detailing the architectural analysis, phased evolution, componentization, data services, and operational insights that enabled scalable, reusable business capabilities across multiple city‑level services.
The pandemic has forced a fundamental shift in R&D management toward resource‑centric, DevOps‑enabled practices while prompting tech leaders to rethink career paths, business models, and growth strategies, highlighting both the challenges and opportunities for technology entrepreneurship in the new era.
The article analyzes why business and development teams often clash over requirements, explains the inherent upper and lower limits of IT production capacity, and proposes practical ways—such as staffing, process optimization, architectural improvements, and demand prioritization—to continuously raise the IT output ceiling while lowering maintenance burdens.
This article outlines the responsibilities of frontline technical managers, detailing project release stages, technical review and documentation standards, code style and development conventions, code management practices, and a comprehensive CodeReview process to ensure quality and efficiency across software projects.
This article explores how developers can transform internal systems into market‑ready products by defining system, product, and commodity, illustrating the conversion process with examples, and outlining practical steps, team considerations, and a roadmap for successful productization.
Kunpeng, a three‑level advertising framework for Xianyu, unifies activity‑scene‑material abstraction, extensible DataFetcher and modular filter libraries, and a global traffic‑mixing algorithm, enabling business groups to self‑service material delivery, achieve 60‑100% conversion gains, cut UV cost by ~40% and halve time‑to‑market.
The article explains, using a 1982 Lisa team story and agile practice observations, why lines of code, iteration velocity, and full staff utilization are unreliable productivity metrics and advocates using global outcome metrics and leading indicators for effective software development management.
The article explains Alibaba's mid‑platform (large‑middle‑platform, small‑front‑end) strategy—originating from Supercell’s R&D methods—detailing its organizational architecture, shared service centers, and how it enables rapid, low‑cost innovation across dozens of business units.
In just 13 hours during the Chinese New Year, Ant Financial assembled a cross‑departmental team to design, develop, test, and launch a free health‑insurance‑supplement service for frontline medical workers, showcasing rapid R&D coordination, product management, and technical execution under pandemic pressure.
This tutorial walks developers through installing ZenTao via Docker, explains core Scrum concepts, and demonstrates step‑by‑step how each role—admin, product owner, scrum master, developer, and tester—uses ZenTao to execute a complete agile project lifecycle.
This report details how the HR system team adopted agile methods—including user‑experience mapping, Sprint 0 preparation, backlog planning, Kanban boards, daily stand‑ups, burn‑down analysis, demo sessions, and retrospectives—to improve delivery speed, quality, and business collaboration.
This article outlines a structured retrospective process for the Eagle Eye financial app project, detailing how to create a safe environment, review iteration goals, collect data, identify improvement actions, set acceptance criteria, and strengthen documentation, testing, and requirement reviews to boost team efficiency and product quality.
The 2019 analysis details how major Chinese internet firms—Tencent, Xiaomi, Baidu, JD, Meituan, and Alibaba—restructured their technical committees and leadership to shift from a saturated user‑growth model to a technology‑driven growth strategy, emphasizing open‑source, cloud integration, AI, and R&D management.
This guide presents a comprehensive set of strategic questions candidates can ask during technical interviews to gain insight into responsibilities, technology stacks, team dynamics, company policies, compensation, and remote‑work arrangements, helping them take control of the conversation and showcase their curiosity.
This article details how a logistics startup overcame severe product‑delivery bottlenecks by reshaping team cognition, visualizing value streams, limiting parallel work, and adopting Specification‑by‑Example, resulting in a ten‑month cycle with 52 iterations, a 15‑billion‑yuan revenue surge, and dramatically faster, higher‑quality releases.
This article shares practical guidelines for recruiters and interviewers to detect poorly crafted resumes, unrealistic experience claims, and superficial technical knowledge by examining candidate age, education, project backgrounds, repeated tech stacks, lack of genuine passion, and by asking targeted verification questions during interviews.
This article outlines three essential principles for responsibly deflecting responsibility in software teams, highlights three scenarios where blame shifting is inappropriate, and provides role‑specific tactics for developers, testers, product managers, and ops to navigate workplace conflicts effectively.
This article explores the true nature of problems, explains why precise problem definition is essential for success, introduces a three‑dimensional framework for assessing severity, categorises problems, and presents "layered" and "dimensional" thinking techniques that help engineers and managers generate innovative solutions.
The article describes how JD.com designed and deployed the VMS version management platform—organized around a 3+1 framework of testing online, integration automation, quality automation, and a single trusted data source—to boost the efficiency of thousands of developers working on mobile applications, achieving up to a 20% increase in delivery speed.
The 7FRESH supplier‑direct‑to‑B warehouse initiative, involving six cross‑functional teams and nearly 60 participants, demonstrates how applying a scaled‑agile SAFe framework—through coordinated PI planning, system‑level integration, synchronized rhythms, and continuous retrospection—can successfully deliver complex, high‑value projects while maintaining team cohesion and delivering business outcomes.
The article examines how Tencent reshaped its identity over a thousand‑day “technology upgrade” by redefining its mission, recruiting top scientists, launching AI and quantum labs, confronting internal silos, and instituting open‑source and middle‑platform strategies to become a true technology company.
The author shares personal insights on transitioning from hands‑on technical work to managing technical teams, covering career progression, skill development, effective hiring, team integration, leadership mindset, and strategies for sustainable growth and collaborative success in security‑focused projects.
This article explains the end‑to‑end process of designing, implementing, and visualizing a quality‑measurement system that aggregates department, application, and individual data, defines evaluation methods, and uses offline Hive calculations to deliver fast, flexible dashboards for software quality improvement.
This article chronicles AutoHome’s five‑year journey of financial information system modernization, detailing the initial 2014 challenges, three development phases, the technical stack transitions, and the strategic outcomes that enabled unified finance operations and data‑driven management.
This article outlines Alibaba’s approach to scaling R&D efficiency across its 50,000‑engineer workforce, detailing the challenges of large‑scale development, agile and DevOps practices, value‑focused delivery, and systematic tools that enable sustained high‑quality software production.
This case study describes how we transformed fragmented offline and phone‑based communication among agents, project managers, and merchant services into a seamless, three‑way instant‑messaging system across the Duoduo selling, new‑house, and merchant‑service apps, boosting efficiency, response speed, and user experience.
This article details how MaFengWo built and refined its large‑transportation development workflow over four phases—initial setup, rapid growth, business expansion, and future outlook—leveraging TAPD for agile iteration, issue tracking, test planning, Gantt‑based resource management, and DevOps integration to boost delivery efficiency and product quality.
This article explains why engineers need business sense, defines the concept, shares product and engineering perspectives, outlines common pitfalls, and offers practical steps and real‑world examples for engineers to better understand and influence business outcomes.
The article explores how senior technical managers, from directors to CTOs, need deep technical detail awareness to succeed in fast‑growing companies, illustrating the pitfalls of neglecting details through personal anecdotes, hiring experiences, and practical advice on team structure and leadership.
The article explains John Heskett’s three‑layer model of designer value—decorator, distinguisher, driver—and discusses why design contributions are hard to quantify in projects, offering insights on how designers can better demonstrate impact on product and business outcomes.
This article provides a thorough overview of the enterprise mid‑platform concept, explaining its military origins, why companies adopt platformization for efficiency and innovation cost reduction, detailing various platform types, benefits, challenges, and practical recommendations for successful digital transformation.
This article examines the concept of a technical middle platform, outlining its purpose, the prerequisites for its adoption, the challenges of implementation, and the trade‑offs between over‑engineering and under‑delivering, while sharing real‑world examples of organizational friction and best‑practice recommendations.
The article shares a senior Alibaba engineer’s journey from a pure technical role to a business‑savvy tech leader, offering practical advice on why business insight is essential for developers, how to acquire it, and the impact it has on career growth and R&D effectiveness.
Facing a thousand‑person, multi‑team, multi‑topic mobile platform, Baidu’s App engineering team built a layered, closed‑loop agile framework—covering organization, business architecture, scope, timeline, risk, and stakeholder management—to streamline delivery, reduce handover costs, and accelerate value.
This article shares candid interviews with three seasoned programmers facing mid‑career challenges, explores their job‑search experiences, and distills actionable advice on handling the mid‑life crisis, leveraging networks, and balancing technical growth with business value.
A reflective essay explores how a tech professional’s neglect of technical depth, hiring practices, and management details can derail careers, illustrated through personal anecdotes, headhunter experiences, and real‑world examples of directors and VPs struggling without solid technical foundations.
This article recounts a four‑year journey at UC, detailing how the author progressed from a single senior engineer to managing teams of over 200, sharing practical insights on demand management, project execution, team culture, rapid product delivery, and organizational scaling.
JD Retail Technology & Data Mid-Platform launched comprehensive agile development in early 2019, achieving 79% agile project adoption and 11% shorter delivery cycles by April 20, recognizing 7 outstanding agile teams and 7 agile champions quarterly to drive continuous improvement.
The article explains Alibaba’s adoption of a ‘big middle platform, small front‑end’ strategy inspired by Supercell, detailing its organizational mechanism, data and product capabilities, and provides a visual overview of the architecture along with links to related in‑depth resources.
In an interview, JD data platform leader Li Wei discusses how dynamic balance between business demands and technical improvement, knowledge computing, and AI-driven product quality control can drive innovation, enhance user experience, and shape future R&D management strategies.
Tao Wen explains that technical depth is demonstrated by how engineers optimize both operation‑maintenance and R&D activities—reducing costs, improving agility, and delivering unique solutions—so interviewers look for a candidate’s proven competitive advantages and the tangible value those strengths bring to the company.
The article analyzes the difficulties of quantifying software R&D efficiency, critiques common measurement methods, proposes two guiding principles—global over local metrics and result over output—and presents a comprehensive set of delivery efficiency, quality, and capability indicators with calculation logic.
The article examines agile transformation as a systematic, multi‑dimensional improvement effort, using YouZan’s evolution to illustrate how project‑manager roles expand from informal coordination in tiny workshops through functional, business‑unit, matrix, and strategic‑business‑unit structures, emphasizing the need to look beyond R&D formalities and consider systemic, time‑delay effects.
The article examines why Chinese software engineers face severe overtime compared to their U.S. counterparts, analyzing product decision processes, the low technical voice in China, infrastructure shortcomings, and cultural attitudes toward work‑life balance, revealing systemic factors behind the disparity.
This guide explains why daily stand‑up meetings are vital for project communication, outlines a step‑by‑step method for introducing them in weak‑matrix organizations, and provides practical tips on preparation, commitment, timing, three‑question format, and continuous feedback to improve team efficiency.
The article outlines Ctrip’s three‑phase technology evolution—from a simple call‑center architecture to layered internet and mobile platforms, and finally to a cloud‑based big‑data and AI‑driven ecosystem—highlighting architectural changes, operational challenges, and strategic lessons for fast‑growing internet companies.
This article explains the purpose, prerequisites, organization, preparation, focus points, execution, and follow‑up of daily stand‑up meetings, emphasizing value‑flow, Kanban visualization, and practical checklists to help teams collaborate effectively and deliver value smoothly.
This article recounts a real‑world agile transformation where a vendor‑centric, zero‑to‑one business system was delivered by iteratively applying agile, lean, and DevOps practices such as JIRA tracking, WIP limits, weekly planning, daily stand‑ups, and shortened feedback loops, highlighting the coach’s role in the trenches.
This article outlines the philosophical mindset, career stages, essential knowledge, and practical habits needed to evolve from a junior programmer to a senior architect, offering concrete steps, role responsibilities, and advice on continuous learning and effective time management.
The article explains why active involvement of business stakeholders in agile practices is essential for delivering value, obtaining timely feedback, and avoiding the pitfalls of waterfall development, illustrated with a Boeing 777 case study and practical recommendations for effective collaboration.
The article presents a comprehensive case study of the C3 credit system’s agile and DevOps transformation, detailing the challenges in configuration and version management, the design of a dual‑mode development and delivery platform, automated pipelines, quality controls, full‑process traceability, organizational rollout, and the resulting efficiency gains, while also including a DevOps recruitment notice.
In this interview, JD Digital's new data asset chief Zhang Xu shares his background, explains how the Outstanding Achievement Award is judged, highlights memorable candidates, and discusses the essential qualities and management principles he expects from technology professionals.
This article explains how Fangduoduo’s R&D team creates an empowering platform by gathering creative talent, fostering a self‑driven culture, integrating product thinking into engineering, and applying DevOps, OKR, and Scrum practices learned from leading Silicon Valley companies.
The article uses a vivid hot‑pot dinner scenario to illustrate common pitfalls in agile software development and explains how structured review meetings—pre‑, during‑, and post‑sessions—help teams deliver the most valuable product efficiently.
The article explains how organizations can increase adaptability by decentralizing decision authority across microservice components, outlines key decision areas to empower, and offers practical guidance for balancing speed, safety, and governance in modern software development.
The article details Suning’s Internet‑plus transformation, describing its strategic “one body, two wings, three clouds, four ends” model, the evolution of its enterprise architecture across three generations, the adoption of cloud, SOA, micro‑services, big‑data and AI platforms, and the accompanying R&D and organizational reforms.
This article explains agile development’s core business goals of faster value delivery and effective learning, defines agile as early value delivery and adaptive response, and presents a comprehensive five‑group metric system—including release capability, demand response cycle, throughput, built‑in quality, and external delivery quality—to assess and improve continuous delivery performance.
This article shares practical insights from an experienced interviewee and interviewer on how interviewers should conduct efficient, two‑way interviews, common pitfalls to avoid, key evaluation criteria such as technical ability, problem‑solving and design skills, and effective questioning techniques to help candidates and interviewers alike.
In this interview, CTO Qiu Hui shares how she built a 600‑person tech organization, emphasizes hiring for shared values, implements rigorous training and performance systems, and uses AI and big‑data‑driven pricing, image recognition, and recommendation engines to create a competitive edge in the used‑car market.
The article examines the rapid evolution of the fund industry's IT demands, outlines global software development trends toward Agile and DevOps, describes Boshi Fund's own DevOps platform transformation, and highlights how these practices drive financial technology innovation and operational efficiency.
A senior project manager reflects on a four‑month, 100‑person‑day software project that collapsed after launch, analyzing five critical mistakes—from neglecting quality and over‑trusting the team to lacking ownership, design, and code review—and shares the concrete steps taken to rescue the product and the key takeaways for future projects.
The article shares a veteran programmer’s journey from facing a mid‑career tech crisis to leveraging data analysis and soft‑skill expertise, illustrating how shifting focus from pure coding to holistic project and business insight can open new management opportunities and sustain relevance in the evolving tech industry.
The article argues that over‑emphasizing business at the expense of technology harms system robustness, proposes quantifying technical KPIs across business, technical, and team contributions, and offers concrete metrics and examples to help engineering leaders restore a tech‑focused culture.
This article explores how software development leaders can transform their management approach by focusing on clear goals, adaptive leadership, strong culture, continuous improvement, transparency, rapid experimentation, and fun to build autonomous, high‑performing teams.
In this talk, the CTO shares practical insights on transitioning from a technical expert to a manager, outlines the dos and don’ts of technical leadership, and offers personal growth strategies to stay hungry and foolish while building effective, purpose‑driven teams.
In this reflective piece, a Baidu veteran shares how ten years of technical work, team leadership, and mentorship shaped his career, offering practical advice on learning, goal setting, and guiding newcomers through the challenges of a fast‑moving tech environment.
The article examines how adopting microservice architecture reshapes companies into flat, small-team clusters, arguing that microservices function more as an organizational design than a pure technical pattern, and outlines principles for aligning teams with business, embracing uncertainty, and simplifying inter‑team integration.
This comprehensive guide outlines the full software project management lifecycle—including initiation, planning, execution, control, and closure—detailing key tasks, deliverables, tools, and best practices for ensuring efficient, high‑quality development.
