This article surveys the most popular software development laws and principles—such as the Pareto, Broken Window, Occam's Razor, Dunning‑Kruger, Peter, Parkinson, Hofstadter, Conway, Murphy, Brook, Postel, Kerckhoffs, Linus, Wirth, and Knuth principles—explaining each rule and offering practical ways to apply or avoid them in real‑world development work.
This article details the design principles, brand‑value strategies, quality control, and cost‑saving measures used to launch the first 58 Daojia premium service center and expand the concept to nearly a hundred physical stores nationwide.
This guide outlines essential steps for planning an application, including defining the problem it solves, identifying target users and goals, understanding current business processes, recognizing key contributors, and creating a project plan to ensure the solution aligns with business needs.
This article explains what bug tracking is, outlines a typical bug‑tracking workflow, describes the elements of a good bug report, lists criteria for choosing a bug‑tracking tool, and reviews twelve popular tools with their features, integrations, pricing, advantages and disadvantages, concluding with recommendations for teams of all sizes.
Project‑oriented R&D cost accounting is required by regulations and management needs to accurately track labor and indirect expenses, enabling precise cost‑benefit analysis, informed decision‑making, and identification of efficiency issues across products and initiatives.
This article defines bug tracking, outlines effective workflows, describes the components of a good bug report, explains what bug‑tracking software should provide, lists key selection criteria, and reviews twelve popular tools with their features, integrations, pricing, pros and cons to help teams choose the right solution.
This guide explains why review meetings are essential for improving product quality, outlines the various types of reviews such as work‑plan, design, code, and management reviews, and provides practical steps and key factors to prepare, conduct, and close review meetings effectively.
Reflecting on China’s Programmer’s Day, the author argues that moving from mere developers to true software engineers—by mastering engineering principles, design, project management, and open‑source culture—is essential for upgrading the nation’s 4 million‑strong software workforce and overcoming low‑quality, involutionary development.
This guide explains seven widely used project‑management tools—including SWOT analysis, the PDCA cycle, 6W2H, SMART goals, and Work Breakdown Structure—detailing their components, practical applications, and how they improve planning, execution, and performance measurement.
By treating postpartum parenting as a structured project—defining kickoff, phases, milestones, daily and weekly task iterations, stakeholder roles, communication protocols, and continuous retrospectives—the author successfully coordinated mother, baby, and family activities during 143 days of maternity leave, achieving all goals and returning to work.
A technical leader at NetEase Yanxuan, with a PhD in applied mathematics, describes building a supply‑chain algorithm team from scratch, categorizing projects as mature, challenging, or innovative, assigning staff by risk, overseeing work through high‑level guidance, engaging with business units to uncover pain points, mobilizing resources for deadlines, and pursuing initiatives while emphasizing resilience, business focus, and a trust‑based workplace culture.
Problem DiscoveryTeam Leadershipcross-functional collaboration
This article explores core project‑management concepts—scope, time, cost, quality—and dives deep into the RACI model, the “Main R” role, risk sources, and practical strategies for balancing responsibility, communication, and risk control in software teams.
This article explains how the Business Model Canvas can be adapted into a Project Management Canvas for agile inception, detailing its nine modules, when to create it, how to interpret each module, and step‑by‑step guidance for building and continuously updating the canvas throughout a project's lifecycle.
This article introduces essential project management concepts, including the five process groups, demand review, risk identification, scheduling, and reporting, to help software developers improve coordination, communication, and overall efficiency in their development workflows.
Guo Xinyi shares how Xianyu’s PMO transformed its project‑management through evolving agile squads, data‑driven OKR‑Scrum‑DevOps integration, and technical branding such as Flutter, establishing feedback loops and metrics that lifted delivery efficiency into the top‑30 % of peer teams while avoiding superficial OKR use.
The article explains why PRD analysis is crucial for developers, outlines three practical steps—clarifying project goals, continuously focusing on the right work, and designing first—and provides concrete questions, domain‑modeling techniques, and activity‑diagram examples to help technical leads turn product solutions into solid technical designs.
This article recounts the author’s experience building a simple Java web application for a university anniversary, covering planning, environment setup, documentation, database design, coding challenges with Spring Boot, Redis, and session handling, deployment on Alibaba Cloud, and the lessons learned about architecture, logging, and monitoring.
This article compares the traditional Waterfall development model with Agile methodologies, outlines Scrum roles and processes, and discusses how teams can balance documentation‑heavy and people‑centric approaches to improve software project efficiency and adaptability.
This article presents a bottom‑up, self‑consistent team management system that categorizes over sixty practices into ten modules across two dimensions, offering actionable insights on time, project, technical, process, institutional, goal, performance, recruitment, talent development, and team building.
This guide walks through a systematic approach to creating, designing, architecting, and operating technical products for developers, covering product design, architecture diagrams, project organization, Git workflows, documentation, CI/CD pipelines, collaboration mechanisms, and post‑release maintenance to help teams deliver successful developer‑focused tools.
This article shares a comprehensive methodology for creating, designing, managing, documenting, and operating technical products—especially front‑end tools—by covering product design, architecture, project organization, collaboration, documentation, website generation, and demand handling, all drawn from real‑world experience.
The article shares key lessons from a recent internal training on clear expression, efficient communication, and team/project management for programmers, illustrating common scenarios such as delayed deliverables, urgent business issues, and cross‑department collaboration, and offering practical strategies for risk escalation, stakeholder coordination, and post‑incident debriefs.
This article explains why designers must adopt project‑management practices, outlines the four key phases—initiation, planning, execution monitoring, and closure—along with tools like 6W2H, STAR and WWH, and offers communication tips to boost influence, efficiency, and overall project success.
This article presents a concise collection of the most practical project management essentials, illustrated through a series of visual slides covering key techniques and tools for effective project execution.
This article explains how concise yet valuable project documentation—README, architecture, and API docs—helps developers onboard quickly, understand system design, and maintain long‑term project health, while offering practical content guidelines and real‑world examples.
This article explains the importance of standardization in multi‑party research projects, outlines the roles and responsibilities of each team member, and details a comprehensive 12‑step workflow—from demand communication to project settlement—to improve quality, coordination, and efficiency.
This article explains how coaching, especially the GROW model, can transform project managers from directive advisors into question‑driven leaders, helping teams uncover their own solutions, increase responsibility, and boost productivity through structured, curiosity‑based conversations.
This article outlines the core concepts of project management, including its definition, goal types, unique characteristics, the triple constraint, comparison with routine operations, typical information‑system project traits, PRINCE2 basics, lifecycle phases, and major development models such as waterfall, spiral, iterative, V‑model, prototype, and agile.
This article presents a concise mind‑map style summary of the essential scope‑management processes for information‑system projects, covering overview, planning, requirements collection, scope definition, WBS creation, scope verification, and control, with visual diagrams illustrating each step.
The article outlines how agile development improves software quality, enhances team collaboration, increases project transparency, reduces risk, accelerates growth, and enables more accurate project assessment, making it a comprehensive methodology for modern, user‑centric software projects.
Although intuition suggests that adding more developers speeds up delivery, software projects often suffer longer cycles due to communication overhead and coordination costs; the classic ‘Mythical Man-Month’ explains why a small, skilled team can be more productive than a larger, less coordinated one.
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.
This guide walks through the full lifecycle of a cross‑team project—defining collaboration, outlining the five‑stage workflow, and detailing practical steps for kickoff, requirement review, task breakdown, technical review, communication, risk control, testing, acceptance, and common pitfalls—to help PMs deliver stable, high‑quality outcomes.
San CLI UI provides a beginner‑friendly graphical layer for San CLI, enabling visual project, configuration, dependency, and plugin management, intuitive build task control with real‑time statistics, and customizable dashboard widgets, all built on a plugin architecture that lowers entry barriers and enhances developer productivity.
This article outlines the typical roles in an internet company, explains how cross‑department collaboration, timeline definition, resource allocation, development‑testing‑deployment phases, and comprehensive project retrospectives work together to ensure successful project delivery.
In this detailed case study, a team describes how they successfully refactored a 30,000‑line advertising engine within a month, covering the system's legacy challenges, preparation steps, execution tactics, testing strategies, and the seven critical takeaways that ensured a smooth, low‑risk rollout.
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.
This article presents a series of mind‑map diagrams that outline the fundamentals, processes, and tools for project communication management and stakeholder management, culminating in a comprehensive overall mind map, with a link to the full‑size image on the author's blog.
This article presents a series of mind‑map images that outline the concepts, processes, tools, documents, and overall framework of project human resource management, with a link to the full‑size diagram for deeper reference.
This article presents a detailed glossary of core project management terminology, covering basic concepts, overall management, scope, schedule, resource, cost, procurement, quality, risk, and communication aspects, each paired with its standard English translation.
This article presents a comprehensive mind map that outlines the core concepts, tools, techniques, improvement methods, and organizational approaches of project quality management, with visual diagrams and a link to the full mind map for deeper reference.
mind mapproject managementproject quality management
This article provides a detailed overview of Maven, covering its purpose, project structure, build lifecycle phases, dependency coordinates and scopes, repository types, plugin mechanisms, aggregation and inheritance, as well as flexible configuration using properties and profiles, all illustrated with practical code examples.
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.
In this reflective article, a former front‑end expert at Alibaba shares half a year of personal growth, detailing how he learned to challenge authority, improve mature technical systems, manage project risks, communicate effectively with product designers, and build professional credibility as a project manager.
This article shares practical strategies for interaction designers to identify and avoid common pitfalls across project initiation, execution, and closing phases, enabling faster, more reliable launches of time‑sensitive activity projects through early involvement, visual workflow mapping, modular components, and coordinated communication.
This article demonstrates how agile principles can be applied to wedding planning by defining clear goals, brainstorming ideas, creating a user‑story map to manage complex tasks, and conducting a post‑event review to assess outcomes and capture lessons for future improvement.
Linus Torvalds explains that developers often overestimate delegation and code importance, emphasizing that user needs trump code quality, that appropriate workflows matter more than tools, and that trust, proper use of SCM, and open communication via mailing lists are key to successful large‑scale projects.
The article follows architect Da Liu’s frustration over being passed over for promotion, revealing seven practical strategies—from reading diverse code and accurately judging project direction to mastering meeting management and version control—that can help engineers transform technical expertise into career advancement.
A project manager recounts how poor quality focus, insufficient team oversight, lack of design, uncontrolled requirement changes, and missing code reviews led to a disastrous rollout, and shares the corrective actions and key lessons to avoid similar failures in future software projects.
The article describes how a software team introduced a 15‑minute daily Scrum standup, defined its participants, duration, and agenda through brainstorming, and observed improved visibility of progress, reduced delays, and enhanced communication, with plans to add a Kanban board for further optimization.
This article explains how the 58APP platform identified design‑consistency problems across its many business lines, defined efficiency, quality, and verification goals, built shared interaction and UI component libraries, established data‑driven metrics, and achieved measurable improvements in publishing rates and overall user experience.
This article compares the traditional Waterfall model with Agile approaches like Scrum, outlining their origins, advantages, disadvantages, key roles, processes, and how teams can balance both methods to improve project delivery and avoid common pitfalls.
The article outlines dubbogo's five‑year evolution, its milestone‑driven roadmap, the launch of dubbo-go-proxy, community recruitment, management practices, tooling, code‑quality measures, and future challenges, providing a comprehensive view of this Go‑based backend framework.
This article concludes a four‑part time‑management series by exploring effective task delegation through the “monkey” metaphor, outlining seven practical steps—from explaining task importance to regular follow‑up—and emphasizing how clear communication and responsibility assignment improve team productivity.
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.
The article outlines three progressive stages for technical staff—from merely following PRD specifications, to understanding business needs and selecting appropriate solutions, and finally to proactively shaping business strategy—while sharing practical methods for demand exploration, project initiation, management, and data‑driven iteration.
This article explains the importance of quality management in projects, outlines its two main dimensions—process quality and product quality—details the multiple benefits of systematic quality control, and provides an eight‑step framework for creating an effective quality management plan.
This reflective article shares 23 practical lessons learned at Alibaba, covering mindset, structured thinking, communication, execution, personal growth, and promotion strategies to help professionals accelerate their careers and lead projects more effectively.
The article recounts Redis creator Salvatore Sanfilippo’s decision to step back from core development, explains his fatigue with open‑source maintenance, outlines the pressures he faced, and discusses how mature projects like Redis can continue thriving after a founder’s departure.
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.
The article compares large‑scale, highly regimented development teams with small, autonomous squads, explaining how the latter achieve faster delivery, higher innovation, and better resource efficiency while still handling complex projects, and discusses Conway's Law and practical implications for modern software organizations.
This article shares practical principles, mindset tips, and concrete planning methods for engineers who want to continuously improve their technical skills, overcome common career dilemmas, and become effective architects and leaders despite a busy workload.
career developmentcontinuous learningengineer growth
This article details how JD.com’s retail teams collaboratively designed, built, and launched the lightweight Jingdong Fast Version mobile app in early 2020, outlining the project’s tight timeline, cross‑team coordination, technical architecture, design simplifications, and the successful on‑time release despite pandemic constraints.
This article explains agile testing principles, contrasts them with traditional waterfall testing, and details how the P1 project applied Scrum testing practices—short delivery cycles, daily stand‑ups, bug triage, continuous collaboration, technical excellence, and streamlined processes—to achieve rapid, high‑quality software releases.
This article identifies frequent agile‑method traps—acting like a project manager, making unilateral decisions, over‑monitoring, slow change handling, and indirect communication—and offers practical remedies to help agile leaders foster trust, autonomy, and faster delivery.
This guide outlines a complete post‑mortem (retrospective) framework—from defining types and preparing meetings to conducting effective sessions and tracking outcomes—helping teams continuously improve project execution and embed a learning‑focused culture across the organization.
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.
The article examines how project management and agile methodologies were applied to China’s nationwide COVID‑19 response, illustrating initiation, planning, execution, risk and stakeholder management, iterative delivery, transparency, and continuous improvement through concrete examples and a structured framework.
The article shares a senior software architect’s multi‑year experience outsourcing projects to India, China and the Philippines, analysing cost differentials, cultural challenges, code quality issues and when offshore development can actually succeed.
cost analysiscultural differencesoffshore development
At iQIYI, Elva leads a versatile PMO that acts like a conductor—standardizing processes, tailoring Scrum, Kanban or waterfall methods, and providing varying levels of support—to coordinate over 100 concurrent infrastructure, product and live‑streaming projects, boost delivery efficiency, and raise organizational maturity without adding headcount.
This article outlines how QA engineers can maximize their impact throughout the pre‑testing, testing, and post‑testing phases of cross‑department projects by understanding system interactions, coordinating with stakeholders, designing comprehensive test cases, monitoring progress, and conducting thorough retrospectives to continuously improve delivery quality.
This article shares practical project‑management secrets from Alibaba Entertainment's PMO, outlining how to structure, coordinate, and execute massive online campaigns remotely by focusing on clear goals, right people, solid plans, effective mechanisms, and thorough retrospectives.
This article analyzes common source‑code management patterns for numerous small projects, identifies their drawbacks, and proposes a hybrid solution that combines a single‑git repository with git‑submodule based sub‑projects, automated shell scripts, and Umi‑based tooling to achieve unified yet isolated development and deployment.
This article explains how the MaFengWo PMO team built a self‑developed PMO system that centralizes requirement data, automates group creation, synchronizes messages and emails, provides risk alerts and weekly reports, ultimately improving execution speed, reducing manual effort, and supporting multi‑business‑line project management.
This guide compiles key product manager interview questions about demand sourcing, priority assessment, requirement validation, translating user needs into solutions, version planning, handling project delays, managing requirement changes, and cross‑department communication, offering concise answers and practical frameworks to help candidates succeed.
The article explains what technical debt is, how it creates a vicious cycle that slows development, outlines common causes such as rushed releases and copy‑paste coding, and offers practical strategies—including measurement tools, incremental migration and full rewrites—to manage and avoid it.
Since 2017 Youzan has built its own Efficiency Platform, evolving from a basic data‑unification tool into a comprehensive collaboration and workflow system that integrates demand management, agile practices, merchant SLA, prioritization, value‑loop analytics, and internal services, embodying efficiency, collaboration, and continuous improvement.
Designers often waste time repeatedly sharing design‑link URLs, but by creating a centralized project‑progress table in Shimo and using link insertion, data validation, and conditional formatting, teams can instantly access design resources, streamline communication, and dramatically improve workflow efficiency.
This article explains the concept of risk, outlines the five key elements of risk management, provides practical templates and examples for identifying and responding to common project risks, and shares a case study with actionable lessons for improving risk handling in agile development teams.
This article explains why measurement is essential for management, outlines a step‑by‑step process for collecting and analyzing efficiency metrics, and shows how to turn data‑driven insights into concrete conclusions and actionable improvement plans for software projects.
JD Central’s 2019 merchant‑center overhaul transformed a fragmented, hard‑to‑use backend into a unified, efficient platform through intensive cross‑team collaboration, rapid component‑based development, and focused user‑experience research, delivering two versions on schedule and earning strong merchant praise.
JD Retail’s technology and data platform adopted agile methods, launched training and coaching, created an Agile Project Management Guide, and achieved a 25% reduction in delivery cycles while 80% of projects now follow agile practices, showcasing measurable efficiency gains.
The author, a former technical director, recounts a three‑month period managing a 20‑person R&D team across four legacy projects, analyzes four critical management mistakes—including over‑estimating team skill, under‑estimating project difficulty, spreading resources too thin, and neglecting dedicated management—and shares concrete reflections and actionable lessons for future leaders.
This article recounts a twelve‑year‑old French government software project that ballooned to over six million lines of C++ code, suffered from obsolete technology, chaotic version control, and absurd management practices, ultimately ending in failure and the arrest of its leaders.
The 2019 China Project Management Development 20‑Year Achievement Forum highlighted Alibaba Infrastructure's award for Best Enterprise Practice, where its PMO shared a layered strategic project management framework that translates departmental strategy into executable projects, offering insights for organizations facing rapid market changes.
This article summarizes Google’s core software‑engineering practices—including a unified source repository, the Blaze build system, rigorous code‑review processes, extensive testing, error tracking, language policies, debugging tools, release engineering, project‑management methods, and personnel development—showing how they contribute to the company’s sustained technical success.
Continuous Integrationcode reviewpersonnel development
This comprehensive guide explains how technical professionals can excel as project managers in internet companies by defining clear goals, aligning people and processes, and navigating each phase—from project initiation and requirement review to scheduling, testing, release, and post‑mortem—ensuring timely, high‑quality delivery.
Effective meetings, essential for solving complex organizational problems, are best managed by applying project‑management principles through three phases—pre‑meeting preparation with clear agendas and materials, disciplined during‑meeting control and consensus building, and diligent post‑meeting follow‑up on action items—tailored to four distinct meeting types.
A technical director recounts a month‑long, troubled e‑commerce project—detailing its background, the cascade of quality and management mistakes, the intensive code‑review rescue, and the hard‑earned lessons on design, delegation, and balancing speed with quality.
This article outlines the nine critical competencies—ranging from analytical thinking and effective communication to automation, DevOps, and project management—that empower software testers to deliver high‑quality applications and thrive in modern development environments.
This article explores the core purpose of system architecture, identifies technical, business, and project-management challenges, and presents a systematic approach—systemic thinking, decomposition, abstraction, and patterns—to effectively design and implement robust architectures.
Business ModelingTechnical Challengesproject management
This article explains how to use GitLab Open API for project creation, code initialization, and team code statistics through Node.js backend services, enabling unified project management and data-driven team productivity analysis.
This guide outlines project naming conventions and step‑by‑step instructions for creating a new Jenkins project, configuring build history, parameterized builds, triggers, Jenkinsfile, and how to build, view logs, and debug the pipeline, illustrated with screenshots.
During a three‑month Flutter internship at Xianyu, a Guangdong University of Technology software‑engineering student migrated from Android to Flutter, rebuilt the publishing page with Fish‑Redux, optimized a pull‑to‑refresh widget saving over 100 MB of memory, mastered the full FDD workflow, and distilled a comprehensive learning roadmap and teamwork advice for future developers.
Drawing on over two decades of experience, this article examines whether project managers should code, outlines the PMP framework, discusses the pitfalls of early promotion to management, and offers practical advice on timing the transition from engineering to leadership roles.
A former programmer shares a candid 13‑year journey from entry‑level coding to tech director, revealing how hard work, evolving leadership styles, reward‑punishment balance, and reflective management practices shaped his success and the pitfalls he learned to avoid.
The article argues that Scrum falls short of true agility, critiques its rigid framework, labels it as fragile when mis‑implemented, and shares personal insights on why simple priority queues often outperform Scrum in software development.
This guide outlines how engineers can succeed as technical project managers by setting clear goals, aligning people and processes, and mastering each phase of the project lifecycle—from initiation and requirement review to scheduling, design, testing, release, and retrospective analysis—while mitigating common risks.
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.