0 views collected around this technical thread.
This article introduces four widely‑accepted code‑quality indicators—cyclomatic complexity, function length, file duplication rate, and class fan‑in/fan‑out ratio—explains how to set thresholds, compare error density across codebases, and apply practical management strategies without degrading quality.
The interview reveals how FAW‑Volkswagen leveraged the CAICT DevOps maturity model to achieve Level 3 continuous delivery for its OTD order‑delivery platform and multi‑functional dealer ecosystem, detailing the standards, implementation steps, performance metrics, challenges faced, and future plans for broader digital transformation.
The article describes how Autohome established a company‑wide, fine‑grained quality measurement system and a comprehensive quality score model that unifies standards across departments, integrates multi‑source data, and drives continuous optimization to enhance user experience and product reliability.
The article explains how teams can adopt nine objective software development metrics—including lead time, cycle time, team velocity, defect rates, MTBF, MTTR, crash rate, endpoint incidents, and code‑quality measures—to continuously improve processes, assess production health, and align engineering work with business value.
The article defines R&D efficiency as delivering higher‑quality, faster value, breaks it into doing the right work, doing it correctly, and ensuring sustainable delivery, then presents a GQM‑driven framework and case studies on testing staff, code review, and process bottlenecks, and outlines a digital decision‑making platform that automates data collection, modeling, and actionable reporting.
This article explains how to automatically monitor and analyze cyclomatic complexity of software projects with the Lizard tool, covering its definition, thresholds, reduction techniques, multi-language support, configuration options, scheduled execution, and result visualization to guide refactoring decisions.
The article examines the challenges of quantifying software R&D productivity, critiques traditional metrics, introduces a set of balanced key performance indicators, and proposes a composite efficiency index (CEI) that combines delivery throughput, deployment frequency, success rate, cycle time, stability, and debt backlog.
The article explains the purpose of software metrics, warns against measuring individual performance and isolated indicators, and outlines key agile testing metrics such as code coverage, acceptance test pass rate, defect density per story point, and automation rate to help teams track progress toward quality goals.
The article uses a humorous story about two development teams manipulating KLOC defect rates to illustrate Goodhart's law and the McNamara fallacy, then presents a comprehensive set of software quality metrics and guidelines for selecting meaningful measurements that truly improve product quality.
The article explains the concept of software testability, outlines controllability and observability factors, discusses cohesion and coupling, suggests practices such as TDD and design patterns, and introduces tools like testability‑explorer and Sonar for measuring and enhancing testability.
This article explains how SonarQube uses static analysis to measure software reliability, maintainability, security, complexity, test coverage and duplication, describes its rule categories, severity levels, issue states, and metric rating scales, and shows why high‑quality code reduces costs and improves safety.
This article explains how SonarQube uses static analysis to measure software reliability, maintainability, security, complexity, test coverage and duplication, describes its rule categories, severity levels, issue states, and quality metrics, and highlights the cost and productivity benefits of high‑quality code.
This article explains how GitLab uses the MR Rate metric to assess engineering productivity, outlines its definition, discusses the challenges of relying on a single metric, and presents four strategies—including improving iteration, setting KPIs, aligning OKRs, and empowering teams—to boost the MR Rate over time.
This article describes the design, implementation, and operational strategy of a comprehensive code‑metrics platform that standardizes coding standards, automates quality checks, and drives data‑guided improvements across multiple development teams, ultimately enhancing code reliability, maintainability, and CI/CD flow.
The article explains, using a 1982 Lisa team story and agile practice observations, why lines of code, iteration velocity, and full staff utilization are unreliable productivity metrics and advocates using global outcome metrics and leading indicators for effective software development management.
This article explains the McCabe metric, the definition and calculation of cyclomatic complexity, its relationship to code quality, and introduces the concept of excessive cyclomatic complexity as a more meaningful indicator for managing software maintainability.
The article explains how to assess a project's code quality using four key metrics, compare error density between codebases, manage legacy code with the Scout Camp principle, and choose reasonable thresholds such as cyclomatic complexity, providing a practical approach for continuous delivery.
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 the difficulties of quantifying software development efficiency, critiques common metric approaches, and proposes a principled framework that emphasizes global, outcome‑oriented indicators across delivery efficiency, quality, and capability to guide systematic R&D performance improvement.
This article explains how software teams can select, combine, and interpret nine essential metrics—including lead time, cycle time, team velocity, defect rates, MTBF, MTTR, and security incident counts—to drive continuous improvement, align with business goals, and ultimately achieve successful outcomes.