This article explains why excessively long classes are hard to read and extend, outlines the problems caused by redundant code and multiple responsibilities, and provides step‑by‑step refactoring techniques using IntelliJ IDEA to extract methods, move members, and create new classes.
The article explains why excessively long classes are hard to read, extend, and maintain, outlines the problems caused by redundant code and multiple responsibilities, and provides step‑by‑step refactoring techniques using IntelliJ IDEA to extract methods, move members, and create new classes.
The article examines the drawbacks of overusing if...else constructs in software, explains why they harm readability and maintainability, and presents ten practical refactoring methods—including table‑driven, chain‑of‑responsibility, annotation‑driven, event‑driven, state machine, Optional, Assert, guard clauses, and method extraction—to simplify or replace complex conditional logic.
This article discusses common challenges encountered when using SonarQube at scale—including data instability across branches, rule configuration for new projects, and project permission management—and presents practical solutions such as branch-specific project naming, Jenkins-driven API automation, and recommendations for purchasing commercial editions.
This article explains why overusing if…else harms code readability and maintainability, outlines ten practical methods—including table‑driven, chain of responsibility, annotation‑driven, event‑driven, state machines, Optional, Assert, and polymorphism—to refactor or replace complex conditional logic, and provides Java code examples for each approach.
The article examines why many software projects deteriorate due to poor code quality, outlines four common pitfalls such as oversized components, low cohesion, tangled logic, and rampant if‑else statements, and presents concrete refactoring strategies—including inverted‑pyramid design, lib/framework separation, Template Method pattern, and rich enums—to dramatically improve maintainability and project success.
This article examines why high‑quality, maintainable code is essential for software projects, outlines four recurring code‑quality problems—including oversized components, low cohesion, tangled logic, and excessive if‑else—and presents concrete refactoring patterns such as inverted‑pyramid design, proper lib/framework reuse, Template Method separation, and rich enum types, while also introducing a CODEX indexing technique for large codebases.
This article explains the fundamentals of static code scanning, reviews popular analysis tools such as Checkstyle, FindBugs, PMD and SonarQube, and details a three‑year evolution of a dealer technology department’s CI/CD integration, automation, metrics, and key success factors for effective code quality assurance.
Long, monolithic Java classes with hundreds of methods become unreadable, hard to extend, and prone to redundant code, so this guide explains the drawbacks of oversized classes and provides step‑by‑step refactoring techniques using IntelliJ IDEA to extract methods, move members, and create new classes.
This tongue‑in‑cheek article enumerates a series of deliberately bad programming practices—from confusing variable names and misleading comments to over‑engineered designs and zero testing—to show how to make code virtually impossible to maintain.
This tutorial walks through configuring GitHub Actions for a Python project to enforce code style, run unit tests, and generate coverage reports using CodeFactor, the wemake‑python‑styleguide action, and Codecov, complete with step‑by‑step instructions and workflow examples.
This article humorously presents a GitHub project's 19 tongue‑in‑cheek guidelines for writing terrible code—from typing less and mixing naming styles to avoiding comments, tests, and documentation—while illustrating each rule with vivid examples and images.
This article presents a tongue‑in‑cheek guide of nineteen "anti‑best‑practice" rules sourced from a GitHub project, illustrating how to deliberately produce unreadable, unmaintainable code by minimizing typing, mixing naming styles, avoiding comments, and other absurd conventions.
An experienced developer recounts how he transformed a cumbersome three‑tier C# data‑center management system from thousands of lines to a concise, maintainable codebase using reflection, generics, and thoughtful refactoring, while sharing practical advice on avoiding code generators, reducing duplication, and embracing unit testing.
This guide explains how to install and configure SonarQube Scanner, set up project analysis parameters, and automate code quality checks within Jenkins pipelines using shared libraries and Groovy scripts, enabling continuous inspection of Java projects.
This guide explains SonarQube's architecture, shows how to deploy it with Docker, and details configuration steps including forced login, LDAP integration, and GitLab authentication, providing code snippets and screenshots for a complete DevOps quality‑management setup.
An overview of eleven essential open-source and commercial tools—including SonarQube, Kritika, DeepScan, Klocwork, CodeSonar, JArchitect, Bandit, Code Climate, Crucible, Fortify, and Codecov—that help developers analyze code quality, detect security vulnerabilities, and integrate seamlessly into CI/CD pipelines across multiple programming languages.
The article explains what technical debt is, how it creates a vicious cycle that slows development, outlines common causes such as rushed releases and copy‑paste coding, and offers practical strategies—including measurement tools, incremental migration and full rewrites—to manage and avoid it.
This article explains how test‑coverage metrics such as line and branch coverage can give a false sense of quality, demonstrates common pitfalls with Java examples and Cobertura reports, and offers practical guidelines for using coverage data to improve testing and code reliability.
The article lists twelve danger signals—ranging from shallow modules and information leaks to vague naming and unreadable code—that reveal hidden complexity in software design and help developers identify and refactor problematic patterns.
This article introduces SonarQube, an open‑source code quality management platform, explains its four main components, integration workflow with IDEs, CI servers and databases, and highlights key features such as rule sets, quality gates, and project dashboards for improving software quality.
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.
In a candid interview, Linus Torvalds shares his pragmatic engineering mindset, explains why Git was his second major project, and demonstrates how a clean pointer‑indirection technique can simplify linked‑list element removal, contrasting it with a more cumbersome approach.
Effective software testing is essential for SaaS startups to avoid costly failures; this guide outlines five key strategies—aligning quality checks with business goals, detailed test planning, fostering a supportive testing environment, conducting user acceptance testing, and measuring code quality with CISQ metrics—to ensure high‑quality releases.
This article outlines fundamental performance‑optimization principles, the hierarchical stages of optimization (requirements, design, implementation), and practical methods such as caching, concurrency, laziness, batching, efficient implementations, and solution‑space reduction, while stressing the balance with code quality and long‑term maintenance.
This reflective essay shares a Huawei veteran’s journey through ten‑plus years of coding, emphasizing solid fundamentals, clean architecture, performance tuning, rigorous change‑control practices, and continuous curiosity about emerging technologies as the keys to becoming a reliable software engineer.
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.
This article explains how to address three common SonarQube challenges—data instability across branches, difficulty assigning quality profiles, and project permission management—by creating per‑branch projects, using Jenkins pipeline scripts with Sonar REST APIs, and applying permission templates to streamline large‑scale code‑quality scanning.
This article compiles practical Java best‑practice tips—from using entrySet() for map iteration and Collection.isEmpty() for emptiness checks to pre‑sizing collections, avoiding magic numbers, employing try‑with‑resources, and cleaning unused code—helping developers write more efficient, readable, and bug‑free code.
This article explains why and how to refactor legacy code by defining refactoring principles, describing common code smells, and presenting concrete techniques such as extracting functions, moving fields, introducing explanatory variables, and reorganizing data and inheritance hierarchies to produce cleaner, more maintainable software.
A graduate student recounts the chaotic state of his research team's C# data‑mining project, highlighting poor naming conventions, oversized classes, overuse of singletons, redundant code, lack of proper inheritance, and other anti‑patterns, while offering concrete suggestions such as using meaningful identifiers, applying the single‑responsibility principle, leveraging LINQ, and adopting MVVM for cleaner, more maintainable code.
Drawing on Ousterhout’s philosophy, the article defines software complexity as cognitive load multiplied by development effort and offers principles such as iterative design, layered architecture, deep modules, information hiding, and purposeful documentation to systematically reduce ripple effects, dependencies, and unknowns in code.
This guide explains how to configure SonarQube scan parameters to automatically include the current GitLab branch name and commit SHA, enabling detailed code‑quality reporting within CI pipelines; it also shows the required command‑line flags and how to set up the Reporting section with GitLab credentials.
This article explores the essential characteristics of clean code, emphasizing high cohesion, low coupling, readability, proper naming, formatting, concise classes and functions, effective comments, error handling, and common code smells, while providing practical guidelines and examples for developers.
This article introduces SonarQube, an open‑source platform for code quality management, explains its seven quality dimensions, provides step‑by‑step installation and configuration instructions (including JDK, MySQL, and scanner setup), demonstrates scanning a project, and summarizes its advantages for developers.
This article explains SonarQube’s architecture, detailing its server, database, plugin library, and scanner components, and describes the typical development workflow from IDE integration and code commit through CI‑triggered analysis, result submission, and code review, including deployment considerations for machines and network placement.
A former intern describes how a top Chinese internet firm suffers from messy code, duplicated libraries, inconsistent logging, poor configuration management, and inefficient development processes, while senior staff defend these practices as necessary adaptations to the company's scale and history.
This article explores four key questions about automated testing: what it is, why it matters, which projects benefit from it, and how to implement it, providing a complete frontend testing framework including unit testing, API testing, functional testing, and benchmark testing.
The article explores what a bug really is, why bugs inevitably appear in software development, and offers practical strategies—such as effective logging, leveraging debugging tools, and keeping iteration sizes small—to locate and resolve bugs more quickly.
This article explores the seven common programming pitfalls—from skipping version control and poor naming to unchecked dependencies, inconsistent formatting, inadequate error handling, and misuse of data types—offering practical advice to write cleaner, more maintainable code.
This guide explains why writing high‑quality code matters, outlines essential principles such as thoughtful design, using tools like SonarQube, proper class, method, variable, and constant naming, and demonstrates refactoring techniques with Java examples to produce more readable and robust software.
This article explains why TSLint is essential for React Native projects, walks through installing and configuring TSLint, demonstrates local and CI checks, and provides a step‑by‑step guide to creating and deploying custom TSLint rules for improved code quality.
A senior engineer reflects on a decade of work at major Chinese tech firms, stressing that clear, responsibility‑driven processes and steady rhythm prevent chaos, while judicious tool choice, appropriate architecture, rigorous bug analysis, consistent style, thorough commenting, security measures, and reusable utilities together boost code quality, maintainability, and development efficiency.
The article shares practical methods for reducing bugs throughout the software development lifecycle, emphasizing early communication with product managers and testers, thorough design and code reviews, mandatory unit testing, continuous integration, and proactive log monitoring to ensure smooth testing and delivery.
The article explores why programmers must continuously adapt to fast‑changing internet technologies, offers practical viewpoints on tracking disruptive trends, deepening fundamentals, and evaluating code quality, and provides guidance on choosing and learning the most valuable skills today.
The article examines the difficulties of developing and sustaining a multi‑million‑line C‑language database, highlighting complex flag‑driven logic, extensive testing pipelines, slow iteration cycles, and the need for automation, modularity, and robust engineering practices to ensure code quality at scale.
This essay explores the history and inevitability of software bugs—from Grace Hopper’s famous moth to today’s massive codebases—examining developer attitudes, debugging practices, and why writing less code may be the only realistic way to reduce bugs.
Pure functions are deterministic, side‑effect‑free routines that always return the same output for identical inputs, and this article explains their definition, observable side effects, practical JavaScript examples of pure and impure functions, and why they improve testability, refactoring, and code quality in modern front‑end development.
This guide outlines key PHP backend practices—including abandoning deprecated mysql_ functions, avoiding unnecessary reference passing, writing efficient queries, validating user input, and embracing modern tools and languages—to help developers produce clean, secure, and high‑performance applications.
The article examines why the software industry produces low‑quality code, identifying three main causes—low expectations, poor programming books, and shortcut‑driven practices—and suggests how developers and leaders can improve code standards.
Improving code quality requires adopting Clean Code principles—clear naming, purposeful comments, consistent formatting, robust error handling, small single‑responsibility classes, shared conventions, and a disciplined workflow that integrates pre‑commit checks, automated static analysis, code reviews, and continuous metric monitoring to ensure each change is cleaner than the last.
This article compiles 75 concise Python coding recommendations covering style, idioms, core language features, standard libraries, design patterns, internal mechanisms, tooling, and performance optimization to help developers write cleaner, more maintainable, and efficient Python code.
The article critiques badly written Spring controller and service code, explains how poor coding habits cause maintenance headaches, and demonstrates a cleaner, AOP‑based approach that reduces boilerplate and improves code quality for backend Java applications.
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.
This article explains ESLint’s no‑empty and no‑empty-function rules, showing how to fix empty blocks by inverting conditions, adding comments, handling silent failures, and using intentional no‑op functions or proper callbacks to keep JavaScript code clean and readable.
This article explains the ESLint rules no‑return‑assign and no‑constant‑condition, shows why they trigger, provides clear examples of problematic code, and offers practical refactoring techniques to resolve the warnings while keeping JavaScript code clean and intention‑clear.
To become a great programmer, ask clear, well‑prepared questions, learn to solve problems independently, never compromise on quality, write deterministic code, embrace unexpected failures, avoid idolizing tools, practice daily, specialize while staying curious about other domains, and relentlessly strive for simple, maintainable solutions.
This article explains how to handle the ESLint "no-fallthrough" and "no-undef" rules, showing when to add explicit comments, convert globals to locals, and why the comment‑based fix is often the most efficient for legacy JavaScript code.
The article examines why many large, well‑known tech companies suffer from messy code, chaotic development processes, and reliance on outdated technologies, exploring the underlying personnel dynamics, reconstruction costs, and the tension between business and technical value.
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 shares five practical recommendations—cultivating genuine passion, treating code as art, writing massive amounts of quality code, staying curious, and focusing on user needs—to help programmers evolve from novices into highly effective, market‑ready developers.
This article explains how to resolve the ESLint "no‑empty" and "no‑empty‑function" warnings by refactoring empty blocks, adding explanatory comments, using noop helpers, and validating callbacks, providing concrete code examples and step‑by‑step reasoning.
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 explains how to set up a PHP project with Composer, PHING, and a suite of quality‑checking tools—including PHPCS for coding standards, PHPCPD for duplicate detection, and Phan for deep static analysis—to automatically enforce code quality and reduce manual review effort.
The Elasticsearch Team Development Constitution outlines a comprehensive set of principles and guidelines—covering design philosophy, code quality, interaction etiquette, and organizational responsibilities—to help the rapidly growing project evolve into a reliable, secure, scalable, and user‑friendly distributed search engine.
Learn how to enhance PHP code quality by implementing unit tests using PHPSpec and PHPUnit, covering SOLID principles, mock objects, test setup, code coverage integration, and best practices for writing maintainable, reliable backend code.
This article outlines the motivation, tool comparison, and detailed step‑by‑step process for implementing static code scanning across Android and iOS codebases, emphasizing the selection of Infer and the integration of scanning results into CI pipelines and issue‑tracking workflows.
This article explains static analysis concepts, why cppcheck was chosen for Baidu's testing workflow, details its architecture, and walks through the creation of custom rules—including a printf misuse detector and a dynamic switch misuse rule—while sharing practical challenges and results.
This article explores why descriptive variable names are crucial for Python code quality, presents practical naming principles, discusses type‑hinting through names, introduces Hungarian notation, and offers actionable tips for defining, using, and cleaning up variables to write clearer, more maintainable code.
This article explains the concept of clean code, why clean code awareness is essential for developers, illustrates common bad‑code patterns with real Java examples, and provides practical guidelines—including formatting, development standards, code‑review rules, Maven conventions, Lombok usage, and refactoring strategies—to help teams write maintainable, readable, and efficient code.
The article explains how to create, configure, and integrate custom Android Lint rules—using Issue, Detector, Scope, and IssueRegistry APIs—to catch crashes, bugs, performance and security problems such as missing Toast.show() or unsafe Log usage, supports incremental git‑based scans, and demonstrates deployment in IDE, builds, pre‑commit hooks and CI for improved code quality.
The article presents five practical concepts—avoiding overly clever tricks, modularizing with divide‑and‑conquer, keeping code IDE‑friendly, ensuring readability through clear architecture and naming, and minimizing branching—to help developers write clean, maintainable code and boost productivity.
This article examines the various programmer archetypes, outlines essential basic, advanced, and auxiliary abilities for backend engineers—including security, performance, architecture, and communication skills—highlights common code smells with examples, and offers concluding advice for continuous self‑improvement.
This article explains key refactoring techniques—Extract Method, Inline Method, Inline Temp, Introduce Explaining Variable, Split Temporary Variable, Remove Assignments to Parameters, and Replace Method with Method Object—showing when to apply each, why they improve code clarity, and providing Java code examples for each transformation.
This article explains what refactoring is, why it improves code quality, readability, and development speed, when to apply or avoid it, the typical refactoring workflow, its relationship with design, and how it impacts software performance.
This article introduces five key aspects of Java code quality—coding standards, duplicate code, test coverage, dependency analysis, and complexity analysis—and explains how Eclipse plugins such as CheckStyle, PMD/CPD, EclEmma, JDepend, and Metrics can be configured and used to assess and improve each aspect.
This article explores the essential tools, methods, and developer habits needed to produce high‑quality, maintainable code, emphasizing why automation alone isn’t enough and outlining concrete code‑review steps that ensure reliability and alignment with product requirements.
Google’s Code Health team, led by Max Kanat‑Alexander, promotes software engineering practices that improve code readability, maintainability, stability and simplicity through internal documentation, code reviews, automated tools, and cultural initiatives, aiming to help engineers make better decisions and accelerate product development.
Google’s Code Health team uses bathroom‑posted programming puzzles to illustrate how deep nesting harms readability, and demonstrates that applying guard clauses and refactoring into short, single‑purpose conditionals can separate error handling from core logic, making code easier to understand and maintain.
This article outlines a four‑step code‑quality ladder—correctness, efficiency, readability, and scalability—offering practical examples, common pitfalls, and best‑practice tips to help software engineers, especially newcomers, elevate their code from merely functional to robust, maintainable, and high‑performing.
Discover eight essential IntelliJ IDEA plugins—including Alibaba's P3C, MyBatis shortcuts, GsonFormat, Stack Overflow search, background image support, Lombok, CodeGlance, and more—that can dramatically improve Java development efficiency and code quality.
This guide explains how to break down a 5‑million‑line Maven codebase into modules, configure SonarQube scanning, and integrate it into a Jenkins CI/CD pipeline for fast, automated code‑quality analysis.
This article explains why ESLint’s no‑return‑assign and no‑constant‑condition rules fire, shows concrete examples—including arrow functions and leftover debug code—and provides step‑by‑step fixes to make the intent of the JavaScript code clear and maintainable.
The article shares a developer's hard‑won lessons from refactoring a ten‑year‑old core system, emphasizing the crucial role of mindset, careful business‑logic analysis, selective task handling, and the use of design patterns to achieve clean, extensible code.
This article shares practical, step‑by‑step methods for programmers to improve code quality, reduce endless bug fixing and overtime, and cultivate disciplined habits such as focused planning, thorough requirement analysis, ignoring unnecessary quality checkpoints, writing readable code, and deliberate practice.
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 examines why software projects often suffer from the paradox of many team members, few deliverables, and heavy workloads, identifying issues such as misaligned roles, poor code quality, communication overhead, mistrust, unclear requirements, and outdated architecture that collectively drain efficiency.
This article compiles seasoned developers' advice on choosing a language, embracing agile delivery, rigorous testing, avoiding premature optimization, and writing maintainable code to help programmers grow their careers and produce high‑quality software.
This article explains why rules like eqeqeq, no‑bitwise, and no‑implicit‑coercion should be avoided, shows concrete examples of problematic code, and provides clear manual fixes to improve JavaScript quality with ESLint.
This guide explains how to add Alibaba’s Java development handbook scanning plugin to IntelliJ IDEA and Eclipse, showing its Blocker/Critical/Major issue levels, real‑time inspection support, batch fixes for legacy code, and step‑by‑step installation procedures.
Alibaba unveiled its Alibaba Java Development Specification (P3C) scanning plugin at the Hangzhou Cloud Expo, detailing its automated IDE checks, multi‑level issue reporting, batch fixes, installation steps for IDEA and Eclipse, and its ambition to become a global open‑source coding‑standard.
This article describes an integrated solution that combines code quality monitoring during development with automated crash issue tracking after deployment, using a custom platform, Jenkins, Gradle plugins, static analysis tools, and rule-based filtering to continuously improve project reliability and performance.
The author reflects on three major challenges—staff turnover, project‑schedule control, and software‑quality improvement—and argues that mastering software‑engineering techniques, tooling, and domain knowledge is essential for effective technical team management.
The article shares practical insights from a Silicon Valley veteran on how professional programmers assume responsibility, write high‑quality code, allocate time for growth, master their domain, adopt thoughtful problem‑solving, communicate effectively, and collaborate without office politics to become true technical leaders.
This guide shows how to configure a Spring Boot multi‑module project using Gradle 3.3 to run SonarQube 5.6.6 analysis by adding the SonarQube plugin, setting repository and classpath, defining sonar properties, and executing the analysis with a simple Gradle command.
This article debunks the myth of writing a million lines of code, explains why code quantity matters less than quality, and offers ten practical steps—including solid fundamentals, coding standards, design principles, refactoring, technical debt management, code reviews, static analysis, unit testing, self‑testing, and leveraging open source—to help developers produce high‑quality software efficiently.
A humorous yet insightful look at the myths of massive codebases, featuring developer anecdotes, realistic productivity calculations, and practical advice on prioritizing code quality, solid fundamentals, and modern tooling over sheer line count.
This article explains why refactoring is essential for maintaining legacy systems, defines refactoring, outlines when to start and stop, describes the step‑by‑step process, discusses code smells and techniques, and offers resources for mastering clean, maintainable software.
The article explains why refactoring is essential for maintaining and evolving legacy code, defines refactoring, outlines when to start and stop, lists prerequisites, describes a step‑by‑step process with testing and version control, and connects refactoring to design principles and large‑scale systems.
This article shares 25 practical guidelines for Python testers, covering YAGNI, test relevance, API design, code simplicity, dependency injection, performance testing, and collaborative coding habits to help developers write maintainable, high‑quality software.
