The AC/DC framework reimagines software development by moving verification from post‑commit CI pipelines to the moment code is generated, letting AI agents write, check, and fix code in a self‑correcting loop, while redefining human engineer responsibilities.
This comprehensive guide explains the importance of thorough code reviews, outlines common pitfalls that make codebases hard to maintain, and provides practical principles, checklists, automation tips, scaling guidelines, clean‑code traits, naming conventions, and solutions to typical challenges such as conflicts, time pressure, and legacy baggage, helping teams improve code quality and development efficiency.
Technical debt, introduced by Ward Cunningham, describes the hidden cost of rushed or sub‑optimal code that degrades efficiency, quality, and developer experience; it arises from intentional or unintentional shortcuts across four dimensions, and can be managed through systematic identification, analysis, resolution, review, and dedicated ownership, yielding more stable, higher‑quality software.
This guide outlines the goals, workflow, review content, and practical methods for effective code review, providing a comprehensive checklist to help teams detect issues early, share knowledge, improve code readability, and foster collaborative development.
Code reviews are essential for ensuring quality, readability, security, and team collaboration; this guide explains their objectives, importance, standards, step‑by‑step workflow, recommended tools, efficiency tips, and provides practical report templates to help teams conduct effective reviews.
This guide outlines the objectives, workflow, key review items, and practical methods for effective code review, providing detailed checkpoints and a checklist to help teams improve code quality, maintainability, and collaborative learning.
This article explains how systematic test case creation, clear verification steps, and disciplined bug tracking improve testing efficiency, ensure comprehensive coverage of core system logic and data flows, and help teams identify root causes to continuously raise software quality despite limited resources.
The article explains how adopting a test‑left‑shift approach—integrating testing activities early in the development lifecycle through stages such as self‑testing, requirement and test‑case reviews, UI/product walkthroughs, showcases, and acceptance gates—can reduce rework, lower costs, and improve overall software quality and team collaboration.
Technical debt, the hidden cost of shortcuts across code, business, and team practices, grows from evolving technology, rapid business changes, and weak standards, but can be managed through disciplined analysis, standardized design, iterative planning, metric‑driven reviews, dedicated resources, and a professional, top‑down mindset.
This article outlines comprehensive code review guidelines, covering principles, optimal timing, scope of evaluation, detailed review criteria such as functionality, complexity, testing, naming, documentation, and offers strategies for handling conflicts and maintaining long‑term code quality within development teams.
The article examines two exemplary software projects—the NASA space shuttle flight‑control system and Donald Knuth’s TeX typesetting engine—to illustrate how rigorous development processes, exhaustive documentation, and systematic error tracking can achieve near‑perfect code quality while shaping modern software engineering practices.
The article explains that design reviews must happen before code reviews to ensure quality and efficiency, describes common code‑review practices, tools like Gerrit and CodeFlow, shares anecdotal experiences, and presents Google’s code‑review statistics to illustrate effective software development processes.
This article explains why code reviews are essential, outlines their benefits and common objections, provides detailed guidelines for developers and reviewers, and offers practical steps for teams to implement and sustain an effective code review process.
This article outlines a practical four‑step framework—defining standards, providing enablement, ensuring controllability, and fostering a collaborative atmosphere—to help testing teams support developers in conducting reliable self‑tests before production deployment.
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.
Undetected bugs arise from vague requirement reviews, incomplete test coverage, lax test execution, limited environments, developer‑introduced defects, and insufficient exploratory testing, so teams should strengthen requirement analysis, design comprehensive cases, enforce strict test adherence, use gray releases, improve code reviews, automate coverage metrics, and adopt disciplined self‑testing and reporting to markedly reduce bug leakage.
This guide explains why systematic code reviews improve software quality, uncover deep design flaws, enhance security, and foster continuous learning among developers, while outlining clear goals, principles, review criteria, best practices, and measurable metrics for successful implementation.
This article explains why front‑end technical design documents are essential, illustrates common pitfalls through a developer story, outlines the differences between front‑end and back‑end design, and provides a step‑by‑step template—including chapters, diagrams, and tool recommendations—to help teams produce clear, maintainable specifications.
This article explains what a frontend design document is, why it’s essential for reducing risk and improving efficiency, outlines the key elements and structure of a good document, and provides a practical template and example workflow for creating comprehensive design specifications in frontend development.
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 comprehensive guide explains why code reviews are essential, outlines their benefits and challenges, describes review formats, participants, focus areas, step‑by‑step processes, key operations, principles, and common pitfalls, providing practical advice and examples to help teams improve code quality and collaboration.
Code refactoring—cleaning and restructuring existing code without changing its behavior—offers numerous benefits such as reduced complexity, improved readability, faster performance, lower technical debt, and better maintainability, and this guide explains its definition, advantages, metrics, techniques, tools, and management considerations.
This article explains why code review is critical, outlines its benefits and common difficulties, describes the TDSQL‑C distributed database architecture, and presents a detailed code‑review workflow, author and reviewer responsibilities, commit conventions, and cultural practices to improve software quality and reliability.
This article reviews key insights from the book “How Google Tests Software”, highlighting Google’s view that quality stems from integrated development and testing, describing the distinct roles of SWE, SET, and TE, and comparing these practices with typical domestic software testing structures.
The article examines Linux’s three‑decade‑old email‑centric development workflow, explains its unique benefits such as detailed commit messages and reliable backporting, highlights the frustrations it causes, and explores possible tool‑based improvements while preserving the process’s core advantages.
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.
The article explains common development models, detailing the steps from requirement gathering to delivery, compares half‑separation and full separation of frontend and backend, outlines their advantages and disadvantages, and reflects on architectural responsibilities in line with Conway's Law.
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.
This article summarizes Google's publicly released engineering practices for code review, outlining the purpose, standards, review workflow, key aspects to examine in change lists, strategies for efficient reviewing, handling conflicts, and tips for writing constructive review comments to improve overall code quality.
This article explains how the Go community drives the future "Go 2" language updates through a standardized proposal selection and evaluation workflow, shows how to locate proposals on GitHub using specific labels, and points to official releases and blog resources for early access and detailed information.
Both Google and Facebook mandate code reviews, with Google enforcing stricter readability qualifications and dedicated tools, while Facebook uses Phabricator; the article outlines responsibilities, TBR handling, review terminology like PTAL and LGTM, and emphasizes resolving all negative feedback before merging.
The article examines the difficulties of quantifying software R&D efficiency, critiques common metric approaches such as time tracking, LOC, and story points, and proposes a holistic, result‑oriented framework that emphasizes global flow efficiency across delivery speed, quality, and capability.
The article examines why developers feel compelled to refactor messy code, illustrates common pitfalls such as mixing refactoring with new feature development, and proposes practical strategies—including separating refactoring from feature work, adopting small‑step incremental changes, and integrating test‑driven development—to manage refactoring projects successfully.
This article examines the importance of code review in fast‑growing development teams, discusses its benefits and common challenges, and provides practical guidelines—including review frequency, time limits, checklists, and cultural tips—to help engineers improve code quality and collaboration.
The article explains how effective software architecture depends on clearly defined business and development roles, the importance of a skilled developer collaborating with the architect, and the need for communication and negotiation to bridge the gap between theoretical design and real‑world project execution.
The article explains how software architecture relies on coordinated roles—business owners, architects, team leads, and developers—highlighting the importance of a dedicated technical lead to bridge business requirements and framework implementation, reduce design friction, and ensure effective communication within the team.
This article shares a veteran front‑end engineer’s step‑by‑step methodology—covering the 3W framework, requirement clarification, timeline estimation, risk exposure, and post‑release monitoring—to help developers consistently deliver high‑quality features.
This article, featuring Baidu QA expert Yang Xiaohui, examines the motivations, benefits, common pitfalls, and strategic considerations for implementing test automation, emphasizing clear goals, stakeholder collaboration, scope definition, timing, and the broader impact on software quality and development efficiency.
Using a vivid restaurant analogy, the article illustrates how original requirements, mid‑project changes, underestimated costs, indecisive features, and client pressure can lead to extensive rework, schedule delays, and chaotic development, highlighting essential product management strategies to handle evolving demands effectively.
