This article reviews a wide range of note‑taking applications, categorising them for team knowledge bases, personal long‑term knowledge management and quick‑capture scenarios, and summarises each tool’s core features, strengths, weaknesses and the types of users it best serves.
This article presents a step‑by‑step method for turning scattered personal prompt knowledge into versioned, testable, and shareable AI workflow assets, covering directory conventions, description design, test case creation, Bad Case feedback loops, Git management, team sharing mechanisms, and a 30‑day rollout plan.
The article recounts a failed enterprise AI rollout, analyzes why strong tools were ignored—fear of responsibility, learning cost, and lack of psychological safety—and offers a three‑step protocol with low‑barrier prompts and conversion scripts to break the ice and boost adoption.
This guide explains how to configure Claude Code’s settings.json file at global, project, and local levels, defining allow, deny, and ask rules, default modes, safe command lists, and hooks, enabling seamless team‑shared permissions and eliminating repetitive permission prompts during development sessions.
The article presents a practical responsibility‑segmentation matrix and three‑step agreement that clarify AI recommendation, human approval, and joint signing roles, enabling teams to avoid blame‑shifting, reduce compliance risk, and make AI collaboration transparent and accountable.
This article breaks down the 2026 Claude Code subscription options—Free, Pro, Max (5x and 20x), Team, and API—by matching each tier to five user personas, explaining usage limits, ideal scenarios, upgrade triggers, and how to decide which plan aligns with your development workflow and workload intensity.
The article analyzes the recurring problem that AI assistants forget project context and fail to retain lessons across sessions, and proposes a two‑part solution—a persistent memory stored in repository files and an explicit self‑learning workflow—that makes AI collaboration transparent, maintainable, and reusable for engineering teams.
The Superpowers + OpenSpec Team Skills library provides a set of workflow modules that guide AI‑assisted development through requirement clarification, design confirmation, change specification, implementation planning, TDD, and verification, ensuring disciplined, traceable, and reliable feature delivery for collaborative projects.
The article explains how coding agents dramatically lower implementation costs, turning the bottleneck in engineering, product, and design collaborations from building code to making high‑quality judgments, reviewing, and context hand‑offs.
OpenWork is an open‑source, locally‑first replacement for Claude Cowork that packages AI agents into a desktop app usable by non‑technical teammates, offering multi‑threaded execution, automation, a reusable Skills system, native Slack/Telegram integration, and a clear comparison against Claude Cowork and Codex.
This article outlines six concrete collaboration practices—role redefinition, hybrid team models, agile ceremony enhancements, tool‑enabled automation, communication barrier removal, and culturally adapted remote work—that together transform testers from execution specialists into value‑driving quality engineers, backed by 2025 Gartner data and real‑world case studies.
Product managers often drown in endless, unproductive meetings that waste time and dilute focus, but by recognizing why communication turns into squabbling, categorizing meetings, leveraging user data, and protecting creative time, they can reclaim productivity and keep their product‑centric mindset.
This article explains how to convert ad‑hoc Claude prompts into versioned, on‑demand Skill modules, covering the concept of procedural knowledge, progressive disclosure, directory layout, SKILL.md metadata, team adoption, common pitfalls, security considerations, and a step‑by‑step 30‑minute rollout plan.
In 2026, as AI takes over routine coding, the decisive factor for senior engineers shifts from writing code to mastering communication—defining ambiguous requirements, verifying AI‑generated solutions, and translating business intent into precise technical tasks.
Boris Cherny, founder of Claude Code, shares a detailed, step‑by‑step set of 13 practical experiences—from parallel multi‑session handling and model configuration to team collaboration, custom slash commands, sub‑agents, and long‑running task automation—demonstrating how to maximize productivity with Claude Code.
Learn how to clone remote repositories, create feature branches, commit and push changes, resolve merge conflicts, and keep your master branch synchronized within IntelliJ IDEA, using practical Git commands and visual tools to streamline team collaboration and avoid common push‑rejected errors.
Factory reimagines software development by organizing specialized AI agents—Code, Knowledge, Reliability, Product, and Tutorial Droids—into a collaborative team that plans, executes, and manages projects through multi‑layered context and seamless tool integration.
This article reexamines software quality, shifting from defect‑centric metrics to a holistic view that combines user value, system reliability, delivery speed, and cross‑team collaboration, and provides concrete company‑level dimensions and test‑team practices to achieve truly high quality.
In the AI‑native era, engineers spend most of their time on meetings and coordination rather than coding, prompting a shift toward networked, task‑oriented teams where AI acts as a collaborative agent, enabling smaller, high‑output groups that focus on value creation instead of mere implementation.
The article outlines ten typical problems that non‑coding software test engineers encounter across business understanding, technical tool usage, and cross‑team collaboration, illustrating each issue with concrete examples and offering practical ways to bridge capability gaps and avoid costly testing pitfalls.
This article explains why a clear branching strategy is essential for collaborative development, compares the most popular Git workflows—including GitFlow, GitHub Flow, GitLab Flow, environment branching, trunk‑based development, release branching, feature branching, and forking—and offers guidance on selecting and applying the best approach for your team’s size, release cadence, product complexity, and compliance needs.
The Dalian University team’s third‑place finish in the 2025 China University Computer Competition’s Big Data Challenge revealed key lessons about data cleaning, focused feature engineering, the power of simple robust models like Random Forest, custom evaluation metrics, and the indispensable role of tight teamwork in data science projects.
This article explores Test‑Driven Development (TDD) as a quality‑focused methodology, detailing its practical benefits, planning strategies, documentation support, team collaboration gains, and the challenges faced in fast‑paced, high‑change environments, while offering balanced advice for integrating TDD with traditional testing approaches.
The article explores how early‑mature teams often struggle later when environments change, offering practical strategies—digital traceability, balanced task delegation, and principled reporting—to navigate cross‑department work, especially in weak‑matrix organizations.
This article details a six‑month, B‑side product team experiment that evolved from a failed AI tool trial to a mature human‑AI collaboration model, achieving 60‑70% automation of development tasks, cutting weeks of work, and establishing a knowledge‑base that lets AI act as a true team member.
This guide explains how to use CursorRules to precisely control the behavior of the Cursor AI programming assistant, covering the rule file structure, global versus project‑specific configurations, rule types, practical examples, best‑practice tips, integration with external documentation, and community resources for continuous improvement.
The article examines how unrestricted wiki editing in companies leads to duplicated, outdated, and low‑quality documentation, contrasts this with the disciplined PR‑based workflow of open‑source projects like Python, and argues that effective documentation governance depends on clear processes and cultural support rather than just tools.
While Agile offers structured, fast‑feedback cycles ideal for commercial product delivery, the Bazaar model thrives on voluntary, decentralized contributions that fuel disruptive innovation; this article compares their principles, advantages, challenges, and suitable scenarios, helping teams decide when to adopt or blend each approach.
This article analyses why current AI agents fall short of being true digital employees, identifies four major obstacles—undocumented knowledge, GUI‑only tools, lack of isolated test environments, and limited memory and initiative—and proposes a comprehensive, six‑step technical and cultural roadmap for creating AI‑native teams that treat AI as a collaborative team member.
This article explains why developers should master project management, outlines common pain points such as inaccurate estimations and dependency issues, and provides practical guidance on progress, quality, and risk management through clear processes, checklists, and collaboration techniques.
Effective interface testing in large projects requires clear test objectives, well‑defined strategies, distinct responsibilities for backend, frontend and testing teams, the use of professional tools for API management and CI/CD, continuous process optimization, and strong communication to ensure high efficiency and quality.
The article explains why companies struggle to hire qualified graduates and why recent graduates find it hard to get jobs, focusing on the high demands of the industry and the multiple technical, learning, project, teamwork, reporting, and client‑communication skills required to become an excellent embedded engineer.
This article explains Scrum@Scale, its core concepts, components, roles, events, and decision‑making teams, showing how organizations can scale Scrum effectively while maintaining agile principles and addressing common challenges such as prioritization, delivery quality, and organizational change.
This article describes how a QA team transformed an impossible‑looking challenge into reality by breaking down a large testing goal into incremental milestones, assigning clear responsibilities, designing focused test cases, and employing proactive risk analysis and code‑review strategies to deliver a high‑quality app within a very short timeframe.
Tencent Health’s medical team deployed Tencent Cloud’s AI Code Assistant, achieving full coverage with roughly 40 % of code generated by the AI; after overcoming early bugs via a vanguard team and feedback loops, they increased per‑capita delivered requirements by 18 %, coding output by 41 %, cut defect rates by 31 %, and earned a 4.8‑out‑of‑5 satisfaction score while planning deeper integration and API‑driven extensions.
This article outlines a comprehensive approach to online stability, covering preventive measures, service governance, capacity planning, incident detection, multi‑dimensional monitoring, alerting, R&D efficiency improvements, team building, and practical guidelines for simplifying, standardizing, automating, and scaling stability initiatives across an organization.
The article outlines a 'six grabs, six releases' framework for project management, detailing how to focus on clear goals, detailed planning, effective teams, communication, risk mitigation, and monitoring while also letting go of perfectionism, hero‑complex, micromanagement, ego, and outdated experience to foster project success.
This article explains the pivotal role of technical architects in bridging business analysis, project execution, and architecture governance, introduces a triangular collaboration model to overcome information asymmetry, and presents a systematic 0→1→N thinking framework with practical methods for identifying key issues, decomposing complexity, and designing future‑proof, decoupled systems.
The article explains how software teams can handle growing production and development scale by applying systematic architectural designs, cloud‑native infrastructure, automation, CI/CD pipelines, and disciplined team and technical‑debt management to maintain efficiency, stability, and quality as the organization expands.
This talk explores how engineers can transition from pure coding to collaborative success and empowerment by adopting T‑shaped skills, mastering the "three meetings and one understanding" framework, applying the WWH perspective, and leveraging AIGC tools to continuously iterate their professional growth.
This article explores how integrating agile development principles—iterative modeling, rapid feedback, collaborative teamwork, and agile tools—can transform traditional linear mathematical modeling into a more flexible, efficient, and accurate process, illustrated with a pandemic‑prediction case study.
The article examines the challenges of applying generative AI to real‑world software development, proposes a collective‑wisdom Copilot that blends team knowledge, AI agents, and IDE integration, and details how Shire’s new version enables sharing, installing, and executing AI‑driven agents across diverse development workflows.
The article explains how a two‑dimensional user story map can help product managers capture, organize, and communicate user requirements more efficiently by visualizing workflows and scenarios, reducing missed details, and fostering clearer collaboration during brainstorming and meetings.
This article explains what MTTR is, why it matters for system stability, and provides a step‑by‑step framework—including monitoring, alert tuning, rapid mitigation, clear role assignments, and post‑mortem practices—to dramatically shorten repair times and improve overall reliability.
In 2024 generative AI has moved from isolated coding assistance to a core, team‑wide engine that augments every stage of software development, integrates with low‑code platforms like NetEase’s Tango, and powers specialized tools such as Copilot, Project IDX, and LangBase to boost efficiency, customization, and code quality across enterprises.
This article explains the importance of code review, outlines its core goals and basic principles, provides step‑by‑step practical guidance with a detailed checklist, shares real‑world case studies and code examples, and discusses metrics and future AI‑assisted improvements to help teams improve software quality.
This article explains the importance of code review, outlines its core objectives and basic principles, describes practical steps and a detailed checklist, shares several real‑world case studies with before‑and‑after code snippets, and discusses the benefits, metrics, and future AI‑assisted enhancements.
StarWish Forest, DeWu’s first growth‑based interactive game, lets users nurture virtual trees by collecting water droplets through daily check‑ins, team planting, PK battles and e‑commerce tasks, automatically advancing through fifteen levels and earning rewards, while its Redis‑driven architecture and modular design enable scalable social engagement and commercial conversion.
The article explains how defensive programming extends beyond simple input checks to include comprehensive data validation, parameter verification, illegal data handling, and collaborative design practices that protect systems from both code errors and external misuse.
This article compiles thirty actionable tips that cover the entire software development lifecycle—from technical selection and tooling to CI/CD, monitoring, and knowledge sharing—helping engineering teams dramatically improve collaboration, productivity, and delivery quality.
This article examines common obstacles that prevent developers from writing clean, high‑quality code—such as tight deadlines, shifting requirements, lack of motivation, poor teamwork, and technical debt—and offers practical strategies, tools, and real‑world examples to overcome them.
This article explains the concept of pair programming, outlines its benefits such as higher code quality and knowledge sharing, examines challenges like increased cost and personality clashes, and discusses its practical applications and alignment with agile development practices.
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.
Software testers play a crucial role in development by ensuring software quality through early involvement, comprehensive testing, innovative methods, continuous monitoring, and team collaboration.
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.
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.
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.
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.
This article explores how effective code reviews foster teamwork, improve code quality, and accelerate developer growth by setting clear goals, focusing on constructive feedback, asking probing questions, mentoring wisely, and keeping review sessions concise and engaging.
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.
WeChat Pay’s team adopted lean, value‑driven development—using TAPD‑enabled value‑stream and agile kanban, small‑batch work, automation, and transparent metrics—to reconcile rapid growth with high‑quality delivery, build consensus across multiple teams, and continuously improve through retrospectives, visual OKR dashboards, and risk‑aware demand decomposition.
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.
