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.
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.
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 shares practical remote‑work guidelines, including replacing daily all‑hands meetings with concise morning reports, scheduling dedicated collaboration windows, maintaining transparent documentation, favoring asynchronous communication, and establishing personal routines to boost individual productivity while minimizing unnecessary interruptions.
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.
The article explores how engineers and managers can use clear standards to assess performance, emphasizing design ability, reliable delivery, collaborative standards, and contributions to team efficiency as essential traits for professional growth beyond mere knowledge accumulation.
The article uses the behind‑the‑scenes process of Friends Season 6 to illustrate agile concepts such as backlog, user stories, MVP, Scrum meetings and continuous delivery, showing how a sitcom’s production can serve as a model for effective R&D management.
Engineers often overestimate their work while managers struggle to set objective evaluation standards; this article explores common self‑assessment biases, outlines four engineer career types, and proposes concrete criteria—design, delivery, standards, and team efficiency—to fairly assess technical contributions and foster growth.
Xianyu transformed its product publishing and editing functions by extracting platform code, introducing the SWAK framework, and decoupling services through RPC, resulting in clearer architecture, reduced code coupling, and significantly improved cross‑team development efficiency.
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.
In the VUCA era, project managers operating in matrix environments must adopt clear responsibilities, emotional intelligence, and strategic questioning to turn awkward interactions with technical experts into productive collaboration, using influence, empathy, and professional insight across all project phases.
The article explains why code review is essential for software teams, describing how systematic reviews catch bugs, spread knowledge, reduce bus factor risk, align trends, improve communication, create useful history, enable precise discussions, strengthen team cohesion, and enhance code readability.
This article explores how engineers across development, testing, and product roles can improve team collaboration and overall effectiveness by adopting a three‑dimensional mindset—product thinking, technical thinking, and engineering thinking—while addressing common misunderstandings and systemic challenges.
The article shares a designer’s journey from UI creation to product ownership, emphasizing the need to observe real users, collaborate across teams, gather industry insights, and turn user pain points into valuable product features for SaaS customer‑service platforms.
The article explains how domain‑driven design helps software teams reach a shared understanding of the problem domain by cultivating requirements through visual collaboration, structured inception and iteration activities, and continuous feedback loops, ultimately improving architecture, reducing miscommunication, and delivering higher‑quality software.
This guide outlines the key features to consider when selecting a task management tool, compares seven popular solutions for developers, and highlights each tool's strengths, pricing, and missing functionalities to help teams pick the most suitable option for improved productivity.
This article shares a step‑by‑step case study of how a small team transformed the Goapi QA testing tool’s user experience by deeply understanding the product, aligning design rhythm with team workflow, fostering cross‑functional collaboration, and building a reusable component library.
The article lists 36 common bad habits that hinder programmers' productivity, grouping them into code organization, team work, coding practices, and testing/maintenance, and explains why each habit reduces efficiency and how to overcome them.
The article explores why engineers often overestimate their work, the challenges managers face in setting fair performance standards, and outlines essential abilities—design, delivery, standards, and collaboration—that distinguish truly effective engineers and drive team efficiency and career growth.
The article describes a Technical Research Group initiative within a tech center, offering several focused sub‑groups (frontend integration, distributed databases, Python engineering, AI, productization) led by experts, limited to eight members each, running Sep‑Dec 2018 with weekly training, demos, and final deliverables, requiring commitment and registration by Aug 30.
The article outlines five typical mistakes new agile testers make—waiting for the next build, not fully integrating with the team, clinging to a quality‑control mindset, relying solely on manual testing, and ignoring the big picture—and offers practical advice for each to foster effective, collaborative testing within agile development.
This article lists 36 common bad habits that reduce programmer efficiency—from poor code organization and teamwork to bad coding and testing practices—and offers concrete advice on how to overcome each to boost productivity and advance your career.
This article examines how DevOps emerged from the merging of development and operations roles, explores automation practices in small and large teams, outlines the three-step DevOps workflow, and discusses the cultural and organizational challenges of adopting DevOps at scale.
This article presents typical developer‑product manager interactions, highlights common wrong replies, and provides concise, professional answers that improve collaboration, reduce friction, and keep projects on track.
This article explains why developers should incorporate diagramming into their workflow, outlines three key uses—understanding problems, facilitating team communication, and merging ideas—reviews various media from pen‑and‑paper to code‑generated charts, and offers practical tips for creating clear, effective diagrams.
Alibaba’s entertainment advertising CRM team replaced a slow waterfall process with a cross‑functional One Team and bi‑weekly iterations, cutting development time from 12 to under 6 days, delivery to under 20 days, improving collaboration, feedback loops, and overall product quality.
This article explores the role of software architects, outlining their responsibilities, essential qualities, differences between internet and traditional enterprises, team dynamics, common optimization practices, and practical advice on growing into an architect and advancing your career.
This article likens the legendary warrior Zhao Yun to modern programmers, outlining three essential practices—self‑cultivation, skill development, and tool mastery—to achieve high‑efficiency coding, and offers concrete advice on design methods, testing, automation, and team collaboration for sustainable productivity.
The article explains how developers can boost their productivity tenfold by focusing on three core questions—what to build, why it matters, and when to act—while emphasizing communication, prioritization, and a product‑mindset over sheer coding skill.
This article explains the benefits of code reviews—early bug detection, improved code quality, knowledge transfer, and stronger team trust—while offering practical tips on what to look for and how to conduct reviews efficiently.
The article outlines seven essential qualities—positive attitude, communication, time management, rapid learning, deep technical experience, teamwork, and user‑centric thinking—that distinguish top developers and offers practical ways to assess each trait during hiring and development.
This guide explains how to use the KJ (affinity diagram) method to unify diverse interpretations of interview data, quickly cluster user traits, and craft compelling persona stories that secure stakeholder buy‑in during early product development.
This article shares candid insights on why many programmers struggle with entrepreneurship, highlighting common misconceptions, overconfidence, lack of teamwork, and the need for an open mindset and practical experience to succeed in building a startup.
The article explains that AI engineers need solid architecture knowledge to turn high‑performing algorithms into real‑world solutions, covering four key reasons: algorithm vs. problem solving, on‑site deployment challenges, scalability, and effective team collaboration.
The article explains why many hiring posts that claim they only need one programmer are misguided, highlighting disrespect, underestimation of effort, misunderstanding of project scope, and premature recruitment, and offers practical advice for both employers and developers.
This article enumerates 35 common bad programming habits—ranging from code organization and team collaboration to testing and maintenance—and explains why they harm productivity, offering concrete advice on how to recognize and replace each habit with healthier practices.
This article explores how front‑end developers can break the cycle of endless revisions by adopting the right mindset, collaborating effectively with product and design teams, embracing component‑based thinking, and developing product‑centric skills that improve efficiency and quality throughout the development process.
After attending the Phoenix Project DevOps simulation in Beijing, I reflect on five key lessons—understanding role responsibilities, leveraging visual tools, focusing on value‑driven goals, applying one‑piece flow, and reducing hand‑offs—to improve operational efficiency and foster a DevOps mindset.
This article explains how well‑crafted design specifications improve multi‑designer collaboration, reduce development redundancy, and preserve brand identity across product iterations, while also highlighting common pitfalls and offering a step‑by‑step guide to building an effective design system for newcomers.
This article shares practical advice on improving personal productivity by optimizing your environment, mastering tools, managing time flow, adopting healthy habits, overcoming procrastination, refining processes, fostering teamwork, and using software like Asana to track work and reflect daily.
The article shares practical insights for engineers transitioning to management, emphasizing the shift from doing to delegating, prioritizing important over urgent tasks, establishing clear rules, fostering team communication, and mastering strategic thinking to drive both personal and team growth.
The article analyzes the root causes of Dev‑Ops conflicts, illustrates typical complaints at each release stage, and proposes concrete measures—shared goals, platform‑driven automation, and cultural alignment—to transform friction into collaborative efficiency.
The article argues that software architects must stay hands‑on—coding, pairing, reviewing, and rotating with delivery teams—to gather timely feedback, exercise effective technical leadership, and avoid the isolated "ivory tower" that hampers agile, high‑quality system development.
This article shares twenty practical software development lessons—from starting with a minimal version and iterating, to effective debugging, teamwork, and continuous learning—offering actionable guidance that seasoned programmers have distilled over more than a decade of experience.
The article examines why software engineers are often seen as hard to communicate with, shares Nicholas C. Zakas' experiences and analogies, and offers practical advice such as involving engineers early, minimizing interruptions, granting creative space, and providing timely appreciation to foster better collaboration.
The article outlines Douban's R&D management philosophy, describing three core constraints—product contribution, proper methods, and technical goals—how they translate into rules, the democratic rule‑making process, cross‑team collaboration incentives, and a balanced performance and reward system.
This guide shares ten practical fault‑management techniques—ranging from proactive attitude and prioritizing incidents to continuous follow‑up and team collaboration—to help operations teams reduce damage, maintain service reliability, and keep users engaged during outages.
Front‑end engineers must blend logical planning, business‑savvy estimation, and design thinking by collaborating with back‑end developers, designers, and product managers to write reusable, maintainable code, anticipate changes, propose user‑focused solutions, and translate static mock‑ups into responsive interfaces that meet both technical and client expectations.
Exploring how various project management tools—from Rally and JIRA to Trello, physical whiteboards, and Confluence—can be selected and applied based on team size, structure, and geographic distribution, this guide helps teams boost efficiency while avoiding tool misuse.
The article critiques common careless attitudes toward code reviews, exposing how pointless debates, condescending comments, exhaustive checklists, and rigid pass‑fail policies hinder collaboration, and offers practical, fact‑based strategies—including constructive questioning and pair verification—to transform reviews into productive, bug‑reducing discussions.
This article outlines the product manager’s role as a communication hub across leaders, design, engineering, and operations, detailing each project phase, common challenges, and practical techniques—such as focusing on product goals and respecting professional expertise—to enhance collaboration and reduce rework.
Brainwriting, a written brainstorming technique, lets participants generate many ideas simultaneously, reduces anxiety, and often yields more concepts than face‑to‑face sessions, making it a powerful alternative for product teams and large groups.
