The article argues that code age or outdated technology alone doesn't define legacy code; instead, when product requirements evolve and the old code must be repeatedly patched, it becomes legacy, while unchanged requirements allow even decade‑old code to remain good.
The article explains how to judge code quality by focusing on stability—handling exceptions, retries, and alerts—and clarity—organizing logic into readable, maintainable steps—illustrated with a real‑world document‑sync example and simple function patterns.
This article presents a curated reading list for software architects, organized by career stages and covering design patterns, code quality, architecture, distributed systems, cloud‑native topics, along with reading principles, recommendations, and a top‑10 book ranking to guide continuous learning.
After years of writing code, the author shares three disciplined habits—anticipating non‑functional scenarios, structuring code to reflect business flow, and adopting spec‑driven development—to improve code quality and resilience in production systems.
The article reviews Matt Pocock’s open‑source “Skills For Real Engineers” repository, explains the four common agent failure modes, details six concrete skills—writing‑great‑skills, codebase‑design, TDD, diagnosing‑bugs, improve‑codebase‑architecture, and prototype—along with their failure patterns, completion criteria, and immediately adoptable actions for teams.
The article defines Architecture Rot as the gradual decay of system design, outlines its four stages—healthy, debt accumulation, degradation, and crisis—details code‑level symptoms, business and technical causes, quantitative detection metrics, and presents a step‑by‑step governance plan including prevention, regular health checks, and incremental refactoring using the strangler‑fig pattern.
The article explains the concept of technical debt, its origins, explicit and implicit forms, sources, interest costs, calculation methods, management practices—including identification, prioritization, repayment strategies, prevention measures, tooling with SonarQube, workshops, OKRs—and debunks common myths about aiming for zero debt.
The article walks through the full lifecycle of a large‑company front‑end scaffold—from pre‑development command simplification and version locking, through template‑driven development, build‑tool integration, commit‑hook checks, and CI/CD publishing—showing how each stage reduces configuration overhead, risk, and duplicated effort.
Over two years I promoted a junior developer to mid‑level, raised his salary, and increased his bonus after he consistently delivered clean DDD‑styled code, handled simple tasks flawlessly, proactively addressed third‑party integration challenges, and demonstrated the ability to take on greater responsibility, illustrating the true criteria leaders use for advancement.
The article argues that detailed specification documents for AI agents end up being as verbose and bug‑prone as actual code, turning a single spec into two code‑like artifacts and exposing a "precision conservation" law that makes AI‑generated code unreliable.
With AI‑generated code now accounting for 55.87% of the 2,000 monthly change requests in the cloud‑storage front‑end team, traditional code review pressure has surged, prompting the team to embed a multi‑agent AICR gate into the CI/CD pipeline that automates context extraction, parallel AI inspections, verification, and feedback while controlling latency and mis‑reports.
The author reflects on the rarity of encountering a truly skilled programmer and explains how such a colleague’s disciplined habits, thoughtful design choices, and thorough exception handling can dramatically improve code quality and accelerate a developer’s professional growth.
In the age of AI‑generated code, the author argues that the true competitive edge for software engineers lies in cultivating a refined “taste” for architecture, design, and judgment, outlining its definition, real‑world examples, and three practical rules to preserve technical dignity.
This article explains why code‑quality issues are a major source of technical debt, introduces SonarQube’s multi‑language static analysis, describes its core features such as multi‑dimensional analysis, incremental scans and Quality Gates, and provides step‑by‑step deployment, configuration, CI/CD integration, best‑practice recommendations, troubleshooting tips and monitoring scripts to ensure reliable, secure and scalable code‑quality management in production environments.
The article argues that AI‑driven “tokenmaxing” is polarizing software teams into a carefree “Lazy” faction that outsources all coding to AI and a overburdened “Craftsmen” faction drowning in massive, low‑quality PRs, eroding mentorship and long‑term engineering skills.
Agent Skills, an open‑source project by Google engineer Addy Osmani, breaks the software development lifecycle into six stages with 24 structured skills, anti‑rationalization checks, doubt‑driven development, and context engineering, enabling AI‑generated code to meet production‑grade quality standards.
As AI coding agents like Claude Code, Cursor, and Codex become common in development pipelines, this article outlines five concrete quality‑control mechanisms—feedback sensors, semantic evaluations, refactor boundaries, provenance trails, and agent surface inventories—detailing tools, trade‑offs, and suitable scenarios to ensure generated code is trustworthy before entering a pull request.
The article traces the evolution of AI in software development, explains why traditional code‑quality processes struggle with Blocker issues, and details how a browser‑automated AI SRE agent can discover, route, and fully repair these problems while keeping humans in the final review loop.
The article argues that blaming code quality masks deeper issues such as uncontrolled requirements, missing engineering systems, and weak management, and it outlines a 2026 quality‑governance framework with practical steps for leaders to create an environment where high‑quality code can thrive.
The article explains why technical debt accumulates through small, ignored code issues, contrasts large refactor projects with daily "pay‑as‑you‑go" fixes, and offers concrete habits, checklists, and AI‑aware strategies for tech leaders to continuously improve code quality.
Despite promises of faster development, AI‑generated code shows 1.7× more defects, up to 2× more security vulnerabilities, and forces 67% of developers to spend extra time debugging, because the probabilistic nature of large language models creates unavoidable hallucinations and context‑blindness.
This article dissects OpenSpec’s four‑step AI programming workflow, exposing why completing the process often still yields buggy code, and proposes five concrete upgrades—including spec reviews, atomic task checks, runtime verification, TDD practices, and archive gate‑keeping—to close the quality gap.
A late‑night payment failure sparked a 30‑point checklist that walks developers through demand clarification, tool setup, rigorous testing, self‑review, CI safeguards, and the right mindset, showing how shifting testing left can prevent bugs before code ships.
The author evaluates a community‑crafted “Karpathy Skills” plugin for Claude Code, applying four concise coding principles, and shows through a controlled experiment that the skill‑guided model produces far fewer superfluous changes—38 lines versus 95—while still fixing the targeted bug and improving code quality.
The article explains that while test coverage helps spot untested code, 100% statement or branch coverage still leaves many scenarios unchecked, discusses statement, branch, and path coverage with concrete Go examples, and offers pragmatic advice on using coverage as a signal rather than a definitive quality metric.
The article lists twelve concrete anti‑patterns—such as over‑splitting microservices, writing megamethods, deep nesting, misleading comments, copy‑pasting code, ignoring logging, and over‑engineering with heavyweight frameworks—that dramatically reduce code readability and make maintenance a nightmare, illustrated through the fictional programmer Er Gou and his bewildered teammates.
This article presents 35 hands‑on Claude Code techniques, each paired with a ready‑to‑use command or prompt, covering project initialization, session management, code quality, architecture review, automation, documentation, dependency handling, debugging, and recovery to help developers harness the AI coding assistant efficiently.
This article walks through a six‑step, AI‑augmented review‑driven development workflow—using Spec‑Kit commands, devil‑style iterative reviews, and TDD—to turn a simple "user login failure lock" requirement into a robust, well‑tested implementation while catching design flaws early.
The article argues that the real value of AI in software development lies not in faster typing but in the developer's ability to judge and refine AI‑generated code, illustrating common pitfalls, concrete examples, and practical habits that cultivate a sense of taste to produce sustainable, high‑quality software.
Superpowers prioritises evidence over intuition by enforcing three hard constraints—test‑driven development, systematic debugging, and verification‑before‑completion—to prevent shortcut thinking, ensure a solid evidence chain, and keep AI‑assisted engineering disciplined and reliable.
The article explores how developers inherit poorly written, uncommented code from departing colleagues, illustrates the pain with real Java examples, and offers a step‑by‑step guide to understand, refactor, and prevent such code‑base sabotage.
The article analyzes the hype around AI coding tools like OpenClaw, exposing false demands, the pitfalls of building agents before real needs, the quality gaps in AI‑generated code, and practical strategies such as spec‑first coding, bottleneck identification, and multi‑model orchestration to improve productivity.
This article introduces five essential Java static‑analysis tools—Alibaba Java Coding Guidelines, CheckStyle, PMD, FindBugs, and SonarLint—explaining their purpose, installation steps, usage methods, result interpretation, and configuration tips to help developers improve code quality and reduce review effort.
A senior developer recounts how AI‑assisted coding feels faster and more fun, yet controlled experiments show it actually slows task completion by 19% and introduces more bugs, while seasoned engineers become over‑reliant, risking loss of design thinking and code‑understanding.
This article details Lalamove's 2025 "Big Cleanup" initiative that identified and removed over 30% of dead Java code and more than 100 obsolete DB fields, describing the tools, SA plugin, BigClean scanner, MyBatis interceptor, and quality‑assurance strategies used to ensure safe, efficient code slimming.
The article examines which parts of a React code review can be reliably automated by AI—such as detecting missing dependencies, unused variables, and test gaps—while emphasizing that architectural decisions, state‑management trade‑offs, and performance reasoning must remain under human control.
Ruff is a Rust‑written Python linter and formatter that claims 10‑100× speed improvements over Flake8, Black, and isort, offering a single‑command solution for linting, auto‑fixing, and formatting, with simple installation, flexible TOML configuration, editor, pre‑commit, and CI/CD integration.
The article argues that basic AI agents built on large‑model APIs and prompts are merely toys, and engineers should focus on high‑barrier, enterprise‑grade tools that require deep engineering expertise to solve complex, high‑risk problems.
The article argues that, despite occasional hallucinations, AI‑generated code now surpasses the average quality of 80% of human programmers, highlighting human code entropy, AI's strict adherence to standards, an autonomous‑driving analogy, and the resulting shift from writing to reviewing code.
The article analyzes three harmful forms of improper encapsulation—over‑encapsulation, fake encapsulation, and chaotic encapsulation—illustrates each with Java code examples, explains the resulting development inefficiencies, extensibility issues, and debugging difficulties, and offers concrete principles to avoid these pitfalls.
The article analyzes three common forms of bad encapsulation in Java—over‑encapsulation, false encapsulation, and chaotic encapsulation—illustrates their hidden risks with concrete code examples, and offers practical principles to restore clear responsibilities, minimal interfaces, and flexible design.
The article identifies three common problems of AI‑generated code—excessive nesting, duplicated logic, and unclear responsibilities—introduces the open‑source code‑simplifier tool with three guiding principles, demonstrates real refactoring cases that cut code size by 60% and halve cognitive complexity, and outlines optimal usage scenarios and installation steps.
The article introduces the open‑source code‑simplifier plugin for Claude Code, explains how it reads project conventions from a CLAUDE.md file, automatically refactors code without changing functionality, and compares its capabilities with ESLint/Prettier and manual refactoring, while offering installation steps, usage scenarios, and best‑practice recommendations.
The article distills Dave Cheney’s provocative Go coding guidelines—abandoning else, using anonymous structs, simplifying conditionals, and isolating main logic—showing how these counter‑intuitive habits reduce cognitive load, improve testability, and lead to clearer, more maintainable backend code.
This article explains what static code analysis is, introduces PHPStan as a leading PHP static analysis engine, outlines its key benefits, provides step‑by‑step installation, configuration and usage instructions, and shows how to integrate and upgrade it within a backend development workflow.
This article explains the Claude Code Hook mechanism, detailing its event‑driven architecture, the ten lifecycle events, concrete security and code‑quality use cases, step‑by‑step script examples, performance and safety best practices, and future directions such as Prompt‑Based Hooks, showing how deterministic control turns AI assistants into reliable, automatable collaborators.
This article details the governance framework, key metrics, and concrete engineering practices used to improve Git metadata performance, code quality scoring, lint enforcement, workflow checkpoints, and code duplication reduction for a large‑scale frontend monorepo, resulting in measurable stability gains.
This guide lists fifteen common bad habits that cripple software projects—such as ignoring version control, poor naming, missing tests, and neglecting security—and provides concrete, actionable solutions for each to help developers produce higher‑quality, maintainable code.
This article explains why static code analysis is crucial for C/C++ development, outlines major standards such as MISRA, CWE and CERT, reviews both commercial and open‑source analysis tools, and provides guidance on selecting the right solution based on project needs, budget and integration requirements.
Proactive data‑corruption handling in PHP is essential because corrupted inputs can cause crashes, security flaws, and costly maintenance; this article explains the risks, why reactive fixes fail, and provides concrete strategies—validation, sanitisation, defaults, testing, monitoring, health checks, and strict typing—plus a practical code example.
This article explains what technical debt is, why it is a business problem, how to measure its cost using unplanned work, provides formulas and examples for calculating wasted capacity, and outlines practical steps to prioritize code quality, architecture alignment, and process improvements for higher team productivity.
Long functions exceeding about 20 lines often hide multiple responsibilities, increase cognitive load, impede testing, and introduce hidden side effects; this article explains the problems, illustrates them with real JavaScript examples, and demonstrates a functional‑programming‑inspired refactor that splits logic into small, pure, testable functions.
This guide presents a comprehensive PHP naming convention handbook, covering universal principles, variable and function styles, class/interface naming, constant rules, pitfalls to avoid, and the PSR standards, offering practical code examples to help developers write clearer, more maintainable backend code.
This article examines why excessive null‑checking clutters code, distinguishes when null is a valid response versus an error, and offers practical alternatives such as assertions, exceptions, returning empty collections, and the Null Object pattern to write cleaner, safer Java programs.
Learn how a single ESLint rule can automatically block stray console.log statements from reaching production, improve code reviews, and enforce clean logging practices without changing your workflow, plus optional stricter settings and pre‑commit hooks for even tighter control.
This article introduces ten widely used Alibaba‑developed Java tools—including the Java Initializr scaffolding service, Arthas diagnostic utility, Dragonwell JDK, code‑style scanner, ARMS monitoring platform, PTS performance tester, AHAS high‑availability suite, EasyExcel, HandyJSON, and the Druid connection pool—highlighting their features, use cases, and links to official sites.
The article examines why AI coding tools often feel like talented but inexperienced interns, identifies memory gaps, understanding bias, and quality risks as core obstacles, and proposes a three‑dimensional partnership model—project memory, precise communication, and multi‑layer quality assurance—to transform AI into a trustworthy collaborator across the software development lifecycle.
The article explains how the single‑commit review mode in Alibaba Cloud Codeup uses AI to evaluate each commit individually, addressing the shortcomings of default bulk diff reviews, detailing configuration steps, recommended scenarios, observed benefits, and its performance trade‑offs.
The article explains how chasing perfect code wastes time, advocates starting with rough drafts to uncover hidden issues, stresses questioning and simplifying requirements, and recommends focused, timed work and essential skills to dramatically improve software development speed and productivity.
This guide explains how Psalm, a PHP static analysis tool, improves code quality by detecting type errors, logical bugs, and security issues, and covers its key features, installation steps, configuration options, IDE integration, automated fixes, and reasons to choose it over alternatives.
Linus Torvalds harshly criticized a Meta engineer's pull request as garbage, using the incident to illustrate how unnecessary abstractions increase cognitive load, why code should be clear and self‑contained, and how modern tools like IDEs and LLMs change the cost of refactoring.
This article compares SonarQube and Codacy, examining their histories, core features, security capabilities, deployment models, and ideal use‑cases, to help teams decide which static analysis solution aligns best with their workflow, technology stack, and compliance requirements.
In today’s fast‑paced software landscape, a comprehensive, automated code quality and security system built around SAST, SCA, IaC scanning, secrets detection, and automated code review is essential for preventing defects, data breaches, and costly downtime across the entire development lifecycle.
This article explores the evolving definition of good code—from a newcomer’s black‑box mindset to a multi‑dimensional quality model—covering stability, user experience, efficiency, cost, code‑review standards, design principles, common code smells, and architectural trade‑offs.
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.
This article explores what makes code truly good by examining functional, stability, user experience, efficiency, and cost dimensions, presenting the "Gold Code" evaluation criteria, discussing design principles, common code smells, practical examples, and how design patterns and layering affect readability and maintainability.
This article reviews four essential IntelliJ IDEA plugins—GitHub Copilot, SonarLint, Rainbow Brackets, and Easy Naming—detailing their core advantages, personal experiences, and how they collectively enhance coding efficiency, code quality, readability, and naming consistency for Java developers.
This article explores how software teams can enhance architecture efficiency by focusing on three core dimensions—stability, performance, and code quality—using practical examples, orthogonal decomposition, and disciplined design to build systems that are reliable, fast, and maintainable.
This article examines how software architecture can be made more efficient by focusing on three core dimensions—stability, performance, and code quality—offering practical insights, orthogonal design principles, and layered coding practices to achieve a robust, fast, and maintainable system.
This article compares SonarQube, Infer, and Clang Static Analyzer for iOS development, detailing their language support, strengths, weaknesses, integration with CI/CD pipelines, and practical usage tips to help teams select the most suitable static analysis solution.
This article explores modern PHP practices that move error handling from runtime try‑catch blocks to proactive strategies such as static analysis, contract programming, attribute‑based validation, and test‑driven development, showing how to build more reliable and maintainable backend applications.
This article explains why code quality degrades as systems grow, introduces five essential static‑analysis tools (Alibaba Java Coding Guidelines, CheckStyle, PMD, FindBugs, and SonarLint), and provides step‑by‑step installation and usage instructions with screenshots to help developers reduce bugs and improve maintainability.
This article explains why code quality matters in growing Java projects and introduces five essential static analysis tools—Alibaba Java Coding Guidelines, CheckStyle, PMD, FindBugs, and SonarLint—covering their purpose, installation steps, usage instructions, and key features to help developers reduce bugs and improve review efficiency.
A new Java developer caused a production NullPointerException while matching third‑party data, and the article walks through reproducing the bug, analyzing each faulty line, and applying defensive programming techniques such as early returns, Optional, Objects.equals, and collection checks to prevent similar crashes.
This article examines the problems caused by overusing if…else statements—such as reduced readability, maintainability, and extensibility—and presents eight practical solutions including table‑driven design, chain‑of‑responsibility, annotation‑driven, event‑driven, state machines, Optional, Assert, and polymorphism, plus additional tactics like method extraction and guard clauses.
This article compares popular static‑code analysis tools for iOS—including SonarQube, Infer, and Clang Static Analyzer—detailing their language support, features, pros and cons, integration methods, and practical usage tips, helping developers select the most suitable solution for their projects.
The article examines the myth that more lines of code equal higher productivity, recounts Bill Atkinson’s -2000‑line protest at Apple, shares community stories of massive code deletions, and argues that code quantity is a poor indicator of true engineering value.
This guide introduces essential Java code‑quality tools—including Alibaba Java Coding Guidelines, CheckStyle, PMD, FindBugs, and SonarLint—explaining their installation, usage, and key features so developers can automate static analysis, reduce bugs, and improve maintainability across projects.
The article lists twelve common anti‑patterns—such as over‑splitting microservices, excessive refactoring without rollout, ultra‑long methods, deep nesting, random naming, misleading comments, copy‑paste code, ignored specs, missing logs, and reinventing wheels—that dramatically reduce code readability and increase maintenance difficulty.
This article explains why software engineering matters, outlines core models like Waterfall and Agile, presents essential design principles such as KISS, DRY, and SOLID, and shows how tools like Git, CI/CD, and project‑management boards turn theory into reliable, maintainable code.
A Qodo survey of 609 developers reveals that while AI coding tools dramatically increase productivity for a small elite, most developers see only moderate gains and many remain hesitant due to trust issues and hallucinations.
This article reveals how common bad coding practices such as over‑engineering, hidden business logic in utility classes, deep inheritance trees, excessive DTO layers, unnecessary interfaces, and contract‑less microservices degrade team efficiency and project quality, and offers concrete, principle‑driven remedies.
This article explains what architecture testing is, why PHP projects need it, introduces tools like Deptrac, PHPArch and PHPMD, shows common testing scenarios, and provides best practices for integrating automated architecture tests into CI/CD pipelines to improve code quality and maintainability.
This article outlines essential Java coding habits—including unit testing with TDD, using Optional to avoid nulls, preferring StringBuilder, proper exception handling, composition over inheritance, Streams API, try‑with‑resources, dependency injection, naming conventions, and design patterns—to dramatically improve code readability, performance, and maintainability.
The article explains Alex Kladov’s two simple yet powerful rules—moving conditional checks out of functions and pushing loop bodies down—to reduce duplicated checks, simplify control flow, and boost performance, especially in batch‑processing scenarios.
This article examines ten frequent Python anti‑patterns—such as mutable default arguments, catching broad exceptions, overly long functions, reinventing the wheel, misusing list comprehensions, excessive lambdas, hard‑coded values, ignoring virtual environments, overusing inheritance, and neglecting code formatting—explaining why they harm readability, maintainability or performance and offering clear, better‑practice alternatives.
The article defines good code as functional and easy to modify, explains why focusing on maintainability and simplicity beats fast but fragile development, lists common signs of bad code, and offers concrete practices like small modules, clear naming, and test‑driven development to boost productivity.
The article lists twelve common but harmful coding practices—such as over‑splitting micro‑services, writing massive methods, nesting deep conditionals, misusing comments, and avoiding logging—that dramatically reduce code readability and increase maintenance difficulty, illustrated with a fictional programmer’s missteps.
This article introduces PHPStan, a popular PHP static analysis tool, explains its benefits, provides step‑by‑step installation and configuration instructions, demonstrates how to run analyses, interpret error reports, troubleshoot common issues, and explore advanced techniques for improving backend code quality.
The article outlines common backend code smells such as over‑engineering, deep inheritance hierarchies, excessive DTO/VO layers, unnecessary interfaces, and contract‑less microservice designs, explains why they harm team efficiency and project quality, and provides concrete Java examples and best‑practice recommendations to avoid them.
This article lists twelve common coding anti‑patterns—such as over‑splitting services, excessive method length, misleading comments, and ignoring logging—that dramatically reduce code readability and maintainability, illustrated with a fictional developer’s missteps and practical lessons for better software engineering.
At Meituan’s technical seminar, experts showcased AI-driven testing innovations—including multi‑agent UI automation, multimodal defect detection, Retrieval‑Augmented Generation for test case creation, and AI‑powered code change analysis—demonstrating how these techniques cut manual effort and boost quality in large‑scale systems handling billions of daily requests.
This article, based on Dave Farley's video, defines bad code by two fundamental criteria, explains how high‑quality code boosts development speed by 44% according to DORA research, explores deep aspects of readability, and offers concrete practices such as TDD, modular design, clear naming, and complexity control.
This article explains how Tencent evaluates code quality at module, function, and implementation levels, describing common code smells such as low cohesion, God classes, developer congestion, God functions, DRY violations, nested complexity, and Bumpy Road, and emphasizes the importance of identifying and fixing these issues to improve maintainability and team efficiency.
This article explains the subtle bugs, predictability issues, scope interactions, and readability concerns that can arise from JavaScript default parameters, and presents explicit argument handling and object destructuring as safer alternatives for large‑scale development.
This article introduces several Java code quality tools—including Alibaba Java Coding Guidelines, CheckStyle, PMD, FindBugs, and SonarLint—detailing their installation, usage, and key features to help developers improve code standards, detect bugs, and streamline code review processes.
This article explores how context‑aware AI, on‑premise model training, autonomous agents, and new metrics for AI impact will reshape software development, boost productivity, improve code quality, and give forward‑looking enterprises a decisive market advantage.
This article explains what makes code high‑quality—functionality, readability, maintainability, efficiency, and documentation—and demonstrates five concrete Python improvements, from type‑annotated inputs to clear naming, robust error handling, comprehensive docstrings, and performance‑boosting caching.
Large tech firms now prohibit the double‑equals operator in JavaScript, favoring triple‑equals to avoid type‑coercion bugs, improve readability, enhance security, and gain slight performance benefits, while static analysis tools enforce this best practice across codebases.
The article reviews open‑source static analysis options for iOS, then compares SonarQube, Infer, and Clang Static Analyzer, outlining each tool’s language support, advantages, drawbacks, CI/CD integration, and practical usage to help teams choose the best solution based on project size, language mix, and reporting needs.
