Drawing on a decade of experience, the article offers a practical handbook for new programmers to become reliable by avoiding common pitfalls—such as false delivery, arbitrary promises, and missed warnings—through weekly goal alignment, disciplined planning, clear requirement discussions, consistent coding standards, thorough reviews, and concise documentation.
This article presents several real-world collaboration scenarios within software teams, highlighting common problems such as unrecognized contributions, unclear responsibilities, and escalating conflicts, and offers detailed analyses and practical suggestions for improving communication, role clarity, and mutual recognition to achieve healthier teamwork.
This article explains the concept, goals, suitable teams, and step‑by‑step process of Mob Code Review (Mob CR), a collaborative code‑review practice that helps teams establish quality standards, educate newcomers, and improve overall code quality through collective inspection and discussion.
The article shares a software test developer’s comprehensive reflections, emphasizing multidisciplinary knowledge, continuous learning, effective communication, attention to detail, and a positive mindset as essential for delivering high‑quality software and advancing one’s career in test development.
Test Automationcontinuous learningquality assurance
Software testers play a crucial role in development by ensuring software quality through early involvement, comprehensive testing, innovative methods, continuous monitoring, and team collaboration.
Test AutomationUser Experiencecontinuous improvement
This guide details how the Big Data Real‑Time Platform department organized a Bug Bash activity to train new staff, enhance cross‑product knowledge, improve product quality, and strengthen team collaboration through structured preparation, execution, and post‑event analysis.
This article shares practical techniques for developers to work more efficiently, covering how to run effective meetings, communicate clearly, set boundaries, collaborate with product and testing teams, and adopt simple project‑management habits that reduce wasted time and improve overall productivity.
This article explores the essential role of Code Review in improving code quality, fostering knowledge sharing, and enhancing team cohesion, offering practical guidance on what to focus on—from naming conventions and comments to architecture, performance, and security—while also discussing reviewer mindsets and cultural adoption.
The article outlines four essential questions—identity, influence, goals, and intimacy—that leaders should help team members answer to establish clear roles, mutual trust, and high performance, illustrating the concepts with examples from surgical teams and practical team‑building advice.
This article details a company’s year‑long evolution of a one‑day Scrum Master training program, covering its motivation, survey‑driven redesign, scenario creation, theory delivery techniques, domino‑based sandbox exercises, key agile practices like time‑boxing and retrospectives, and the resulting growth of a sizable certified Scrum Master talent pool.
This article outlines practical strategies for enhancing code quality and development efficiency, addressing challenges such as time pressure, frequent requirement changes, lack of self‑motivation, poor team communication, technical debt, insufficient automation, and feedback mechanisms, and includes a real‑world case study and certification promotion.
The article explains the overall architecture of remote development, why it is needed, how it improves team productivity and resource control, and details JetBrains' remote development solution that lets developers work on powerful cloud servers through a lightweight local client.
Relying solely on defect counts as a KPI fails to reflect a software test engineer’s true performance, so a multi‑dimensional evaluation—including test coverage, defect severity, automation, efficiency, problem‑solving, and teamwork—provides a more objective, comprehensive and fair assessment.
The article recounts a Go project's evolution of configuration handling—from hard‑coded DB credentials to a unified global struct and finally an init‑based implicit loader—highlighting how each teammate’s approach reflects distinct mindsets, knowledge gaps, and productivity trade‑offs, and invites readers to consider their own collaboration preferences.
This article shares practical experiences, challenges, and best‑practice advice for front‑end engineers building reusable infrastructure platforms, emphasizing long‑term planning, cross‑team collaboration, incremental delivery, data‑driven validation, and the importance of balancing low‑level architecture with user‑facing product features.
This article explores horizontal management—coordinating with developers, designers, and product staff—through four concrete stories, highlighting communication pitfalls, bug‑tracking challenges, and practical steps to improve cross‑functional teamwork and project quality.
R&D managementbug trackingcross-team communication
This article explains why analyzing an organization’s structure, collaboration patterns, and risks is crucial for data product success, outlines an ideal data‑centric organization model, shares real‑world examples and practical steps, and provides a Q&A on common challenges faced by product teams.
data productorganization analysisproduct management
The article outlines ten frequent pitfalls that organizations encounter when adopting DevOps—such as out‑of‑order delivery, misinterpreting DevOps roles, neglecting database automation, and ignoring security—and provides practical guidance on planning, collaboration, and balanced speed‑quality trade‑offs to achieve successful DevOps outcomes.
The article argues that DevOps is a practical approach to achieving continuous delivery, emphasizing that the teams who build the software must also run it, monitor production, and take responsibility for reliability, especially during unexpected incidents such as off‑hour outages.
This guide explains how to prepare, execute, and wrap up online agile co‑creation workshops by defining clear goals, selecting the right participants, assigning organizer roles, and choosing effective digital tools to ensure productive remote collaboration.
This article explains what a post‑mortem (复盘) is, why it is essential for individuals, teams and organizations, and introduces six practical analysis methods—including 5M1E, 5 Why, 5W2H, fishbone diagram, team co‑creation, and the Person‑Event‑Time‑Place‑Thing framework—along with templates and visual aids to help practitioners conduct thorough reviews.
The article outlines a systematic approach for technical managers to transform ad‑hoc performance fixes into reusable, organization‑wide governance processes that include problem definition, identification, handling, best‑practice patterns, and continuous monitoring.
Process OptimizationTechnical Governanceperformance management
The article reveals that professional developers spend most of their time maintaining large codebases, navigating domain knowledge, writing documentation, handling incompetent teammates, assuming bugs, estimating work, and attending meetings, emphasizing that delivering business value outweighs writing elegant code.
Software engineers rarely build entire systems from scratch; instead they spend most of their time navigating large codebases, documenting, estimating, handling uncertainty, and collaborating with imperfect teammates, emphasizing business value over elegant code, and learning practical skills that university curricula often overlook.
This article analyzes common team collaboration challenges, maps them to Patrick Lencioni's five dysfunctions, and presents concrete agile practices—such as welcome/farewell rituals, life‑journey sharing, pair metrics, speedback, and rotating on‑call duties—to build trust, encourage healthy conflict, increase engagement, avoid responsibility avoidance, and focus on results, ultimately fostering a high‑performing, self‑organizing team culture.
In business‑driven companies, developers must prioritize understanding the business, foster cross‑team collaboration, and broaden their perspective beyond pure coding, because technical prowess alone is insufficient for survival, growth, and career advancement.
This comprehensive guide explains why code review matters, shares real‑world practices from leading companies, outlines concrete steps for submitters and reviewers, warns against common pitfalls like DRY violations and poor pagination, and offers actionable tips to make reviews effective and sustainable.
Drawing on three years of product‑team experience, the article outlines how OKR tracking evolved through a “Do‑Not” start, process consolidation, and an information‑driven timeline, emphasizing weekly summaries, bi‑weekly meetings, monthly celebrations, quarterly reviews, a lightweight “callme” tool, and core principles of transparency, positive incentives, and a happy team culture, while urging each team to tailor its own rhythm for continuous improvement.
In Chinese internet firms, front‑end development has grown into large specialized teams, and DeWu’s API‑documentation‑driven development model—presented by former Alibaba leader Zhu Junbiao and explained by Chen Ziyu—demonstrates how an API‑driven workflow on the Mooncake platform resolves collaboration bottlenecks and boosts development efficiency.
The article offers practical guidance for software architects on building adaptable product strategies, emphasizing the need for implementation‑focused design, realistic resource planning, customer‑oriented goals, iterative hypothesis testing, and cross‑functional team collaboration to ensure sustainable architecture execution.
This article outlines the original test case review workflow, identifies its inefficiencies, and presents a comprehensive set of improvements—including pre‑review preparation, role assignments, meeting conduct, post‑meeting follow‑up, and presentation techniques—to help QA teams conduct more efficient and effective test case reviews.
This article outlines comprehensive guidelines for keeping customers happy, managing projects, designing robust APIs, conducting thorough code reviews, shaping strategic direction, ensuring observability, and fostering research, all aimed at building resilient and high‑performing engineering teams.
The article examines the challenges of moving large, multi‑team software organizations from waterfall to lean‑agile practices, offering concrete tactics for product planning, cross‑team coordination, integration, testing, and release, and concludes with a note on an upcoming DevOps hackathon.
This article explains the differences between remote and distributed teams, outlines the benefits of a distributed model, and provides practical tips, communication strategies, meeting structures, video documentation methods, and team‑management practices for successfully running a distributed software development project.
This article explains how adopting a DevOps culture—by forming true functional teams, shortening release cycles, and aligning shared goals—can resolve the conflicting objectives of developers and operations, enhance communication, and enable more frequent, higher‑quality software deliveries.
Mob CR, short for Mob Code Review, is a team‑oriented, five‑step process that uses collective code inspection to establish shared quality standards, educate newcomers, and align developers on better design and implementation practices.
The article explains why testing aims to ensure software quality, outlines how testers can avoid being blamed by documenting bugs, following clear hand‑off processes, collaborating on urgent test items, and fostering a team culture of responsibility and continuous improvement.
In 2021, Xinwang Bank’s digital-native team tackled tight deadlines, tool migrations, personnel shifts, and intense debates to successfully achieve a Level‑3 DevOps continuous‑delivery assessment for its distributed consumer‑credit core system, demonstrating how coordinated effort and containerization can boost operational excellence.
The article explains that technical debt stems not from clumsy coding but from poor communication and inadequate domain modeling, leading to fragmented abstractions, excessive boolean flags, and ultimately software bankruptcy, and suggests collaborative, model‑driven practices to reduce it.
This article examines the challenges of improving research and development efficiency in digital-era enterprises, presents real-world success and failure cases, outlines the roles of business, tool, coaching, and organizational teams, and offers practical do's and don'ts to achieve sustainable, business‑driven efficiency gains.
This article shares personal notes and a mind‑map on Domain‑Driven Design, explaining effective modeling elements, knowledge digestion, continuous learning, and deep modeling to help development teams build structured, collaborative domain models that align code with business logic.
This article explains what technical debt is, why it matters, and provides practical guidance on avoiding blame, discussing risks, prioritizing work with techniques like delay cost and ICE/RICE, and implementing concrete strategies to allocate effort and reduce debt in software projects.
This article outlines six practical metrics—unified backlog, user‑centric requirement description, consistent requirement flow, short lead time, high iteration completion rate, and stable iteration velocity—to help teams distinguish superficial agile ceremonies from truly effective agile execution.
This article lists twenty common bad habits of programmers—from inconsistent terminology and poor documentation to neglecting testing and teamwork—explaining why each harms productivity and offering concrete advice on how to develop professional coding practices.
The article outlines twenty common bad habits of programmers—from inconsistent terminology and poor documentation to neglecting official resources and teamwork—explaining why each is detrimental and offering practical advice for cultivating professional competence and collaborative success.
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.
This article examines common pitfalls in code reviews, outlines clear goals and principles, and provides actionable strategies for designing, reading, and sharing code to boost quality, speed, and team learning while avoiding time‑wasting habits.
This article explains how agile architecture differs from traditional approaches, outlines the full lifecycle of agile architecture, defines responsibilities, introduces the role of an architecture owner, and provides practical guidance for modeling, scaling, communicating, and evolving architecture in large‑scale agile projects while avoiding over‑engineering.
This article explains why high‑quality technical documentation is essential for teams and organizations, outlines common reasons engineers avoid writing docs, and provides practical methods—such as treating docs like code, defining the audience, clear classification, and systematic review—to create and maintain effective documentation.
This article outlines why code review matters, defines the roles of authors and reviewers, details a step‑by‑step CR workflow, sets clear review standards, and explains how disciplined reviews boost code quality and team efficiency in frontend development.
This article outlines how the Meishi internal office platform enhanced team collaboration by redesigning its calendar feature, detailing problem discovery, design principles of simplicity and flexibility, integrated functionalities with contacts, attendance, meeting rooms, and the agile, iterative development process that led to improved user experience.
The NetEase News iOS team adopted a three‑layer componentization strategy—foundation, common, and business—standardizing code conventions, Git workflow, and CI‑driven reviews, encapsulating third‑party libraries, managing dependencies via injection and mediators, and distributing binary pods, which reduced the main project to a single file while expanding reusable components to over 250, achieving low coupling and high cohesion.
This article offers practical engineering guidance on when and how to refactor client‑side code, emphasizing planning, incremental changes, systematic approaches, tooling, and team coordination to improve code quality while minimizing risk and maintaining system stability.
This article examines daily stand‑up meetings in agile software development, outlining essential practices, common pitfalls, and detailed patterns—including participant roles, question formats, speaking order, timing, energy‑keeping techniques, and autonomy‑building strategies—to help teams run concise, valuable syncs.
This article explores the core concepts of clean code for JavaScript, covering code smells, technical debt, refactoring, readability, writing code in English, and team collaboration techniques, while providing practical examples and tooling tips for maintaining high‑quality code.
This article uses a real‑world example of a new developer tasked with creating project documentation to illustrate common pitfalls and offers a step‑by‑step framework for defining purpose, breaking work into manageable stages, coordinating teammates, tracking progress, and delivering tangible results that reinforce reliability and personal growth.
This article compiles lessons from various engineering blogs on why and how to conduct code reviews, covering their role in quality assurance, team learning, pull‑request preparation, constructive communication, and the importance of praise and positive tone.
This guide explains why code reviews are essential for maintaining product quality, preventing technical debt, fostering team knowledge sharing, and improving developer skills, while also addressing common challenges, best‑practice processes, and practical examples to help teams implement effective reviews.
This article compiles key lessons from various engineering blogs on why code reviews matter, covering their role in quality assurance, team growth, effective review checklists, preparing pull requests, humane communication, and recognizing contributions, providing a comprehensive guide to improve review processes.
Code Review, a crucial yet often overlooked development practice, enhances code quality, promotes team knowledge sharing, enforces consistent standards, and improves maintainability, while the article outlines its benefits, practical guidelines, timing, formats, and specific expectations for reviewers and reviewees to foster effective adoption.
This article explains the multiple benefits of code review—from knowledge sharing and improving code quality to enforcing team standards—and provides practical steps, cultural tips, tool recommendations, and workflow guidelines to help development teams adopt effective code review practices.
This guide offers practical advice for agile developers, covering stand‑up meetings, sprint planning, tracking progress, story points, and teamwork to help teams thrive in fast‑paced, remote‑first environments by emphasizing efficient communication, realistic planning, and continuous improvement.
This article explains the importance of code review for improving code quality, fostering team knowledge sharing, enforcing consistent standards, and provides practical guidance on allocating time, choosing review formats, timing reviews, and setting clear expectations for reviewers and reviewees.
This article explains how product managers can overcome inconsistent requirement understanding, rework, and delays by using user story mapping—a collaborative, visual framework that involves all stakeholders to achieve shared insight, identify pain points, and drive effective product design.
Requirement ConsensusUser Story Mappingagile-practices
This article examines the often‑tense relationship between product managers and developers, identifies the main sources of friction from both sides, and offers a structured three‑step approach—including clear direction, rigorous use‑case work, and five communication techniques—to achieve sustainable, win‑win collaboration.
The author recounts his 2012 MySQL interview experience, describes the flat, globally distributed InnoDB team structure, details the typical bug‑fix workflow, lists major InnoDB features he contributed to, and reflects on the lessons learned before moving to Tencent Cloud's database division.
This article explores the nuanced relationship between Agile and DevOps, clarifying common misconceptions, detailing how Scrum and continuous delivery intersect, and presenting the three‑layer DevOps model that helps teams integrate cultural, technical, and delivery practices for better collaboration and value delivery.
Code reviews are essential for maintaining product quality, reducing technical debt, and fostering team knowledge sharing, yet they face challenges like time constraints and subjective biases; this guide outlines why reviews matter, their benefits, common pitfalls, formats, participants, focus areas, processes, key operations, principles, and typical issues with practical examples.
This article examines seven typical misconceptions in software development—from focusing on tasks instead of demand to favoring batch releases over continuous delivery—and offers practical guidance on improving flow efficiency, cross‑functional collaboration, code quality, and automated testing.
This article shares the author's journey from internship to employment at ZCY, highlighting the company's culture, mentorship, and professional growth opportunities.
This article presents a cloud‑based shared proxy solution that addresses common pain points of local proxy tools by enabling multi‑user configuration sharing, isolation, mock & host management, data persistence, analysis, and monitoring, thereby improving development and testing efficiency for teams.
This article examines the debate over whether a Product Owner should join the Daily Scrum, presenting arguments for and against participation, referencing Scrum guidelines, and offering practical tips for making stand‑up meetings efficient and effective.
This article outlines a seven‑step DevOps transformation roadmap, explaining how companies can select value streams, build cross‑functional teams, map processes, adopt best practices, leverage tooling, and scale the change while managing cultural and organizational challenges.
The guide presents six communication strategies for product managers and programmers, stressing clear, visual requirement presentation, thorough verification, professional bug reporting, thoughtful handling of last‑minute changes, face‑to‑face discussions for complex topics, and standardized documentation to align technical and non‑technical teams and boost project efficiency.
Agile methodologyBug Reportingdeveloper communication
This article explains the true purpose of code review beyond bug hunting, explores its cultural and quality benefits, and offers seven actionable recommendations—including small batch reviews, frequent cycles, choosing the right reviewers, rapid feedback, modern tools, pair programming, and blending online with offline sessions—to make code reviews more effective.
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.
The article explains how adopting a concise, shared checklist for code reviews can reduce subjectivity, improve team trust, and ensure critical quality and documentation standards are met across software projects.
The article argues that keeping software architects hands‑on with coding improves team communication, design accuracy, tool awareness, and product ownership, while highlighting the pitfalls of architects staying away from code and offering practical solutions for better collaboration and architecture evolution.
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 article presents a comprehensive guide based on Google's OKR playbook, explaining the purpose of Objectives and Key Results, detailing practical rules for writing good OKRs, highlighting typical mistakes, and offering self‑assessment tests to help teams implement OKRs successfully.
The article outlines a strategic framework and practical solutions for product‑technology PMOs, emphasizing stakeholder perspective, purpose clarity, communication, and documentation, while addressing unclear planning, long delivery cycles, and coordination through regular OKR meetings, defined milestones, iteration rhythms, and integrated platforms, resulting in markedly higher integration rates and faster releases.
The article argues that the common belief that architects need not code is a misconception, explaining how hands‑on coding improves architectural decisions, team collaboration, design quality, and product ownership while also addressing potential drawbacks and offering practical solutions.
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 article explains why code review is essential for improving code quality, fostering team knowledge sharing, enforcing standards, and reducing technical debt, and provides concrete guidelines on making code review a mandatory, cultural part of the development workflow with practical tips and tool recommendations.
The Q Team from Xiaomi’s Information Technology Department documented a six‑step agile transformation that defined roles, built JIRA boards, aligned iteration calendars, integrated product and testing, shifted quality activities upstream, and established daily cross‑city video syncs to improve overall quality management and team efficiency.
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 article details how a supply‑chain contract‑manufacturing team, guided by Agile mentor Wang Lijie, assessed its current practices, organized project requirements, established iterative workflows, held daily stand‑ups and retrospectives, and outlined future steps such as continuous integration, automated testing, and BDD to achieve a more flexible, value‑driven development process.
Xiaojie, a software engineering graduate, turned his Youzan internship into a full-time Android developer role by inventively cutting Android incremental compile time from minutes to seconds, earning praise for his proactive problem-solving, thriving in the company’s supportive, growth-focused culture.
This article explains why user participation matters in B2B products, outlines how to involve users throughout the development cycle, improve designers' and team members' sense of ownership, and offers practical steps to create a more collaborative and effective product ecosystem.
This guide explains how to adopt disciplined Git habits, use Git Flow branch models, configure SourceTree and GitLab, and follow a structured development process that covers committing, rebasing, merging, testing, releasing, and hot‑fixing for smooth team collaboration.
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.
This guide explains how to adopt solid Git habits, write meaningful commits, use interactive rebase, configure push and pull behavior, choose between merge and rebase, apply the Git Flow branching model, and set up SourceTree and GitLab for smooth team collaboration.
This article explains how to effectively apply Git in a team setting, covering commit habits, branch management with Git Flow, tool configuration, merge strategies, and release processes, offering practical examples and visual guides to improve collaboration and maintain a clean development history.
This article explains why code review is essential for software teams, covering its benefits for knowledge sharing, code quality, and team standards, and provides practical guidelines on making code review a mandatory step, fostering a review culture, and applying effective techniques and tools.
This article explains how architecture remains a vital part of agile software development, covering agile‑first approaches, lifecycle‑wide modeling, ownership roles, scaling strategies, demand‑driven design, multi‑view modeling, myth busting, and practical guidance for lightweight, collaborative architecture in modern organizations.
This article explains the multiple benefits of code review—including knowledge sharing, improved code quality, and enforcing team standards—and provides practical steps, cultural tips, and tool recommendations to make code review a mandatory, effective part of any development workflow.
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.