Tagged articles
code smell
10 articles · Page 1 of 1
The article explains the origin of the term “code smell,” expands the classic catalog to over 50 modern smells, and demonstrates how the AI‑powered /smell skill automatically scans a sizable Go project (Gitlawb/zero), identifies issues such as God objects, long files, and hidden performance hotspots, then generates a prioritized refactoring roadmap.
AI analysisGocode smell
0 likes · 14 min read

The article introduces the open‑source /smell skill, an AI‑powered code‑analysis tool that scans a codebase, identifies architectural anti‑patterns, code‑level smells, and performance hotspots, and generates a detailed markdown report with severity rankings and refactoring suggestions.
AI code analysisGocode smell
0 likes · 12 min read

This article explains Java's labeled break statement, showing its syntax, a practical example with code, discusses its potential as a code smell, outlines appropriate use cases, and offers guidance on when to prefer refactoring for clearer control flow.
Best PracticesJavacode smell
0 likes · 6 min read

This article explains twenty‑five typical code smells—such as duplicated code, long methods, large classes, and excessive parameters—and provides concrete refactoring techniques like Extract Method, Extract Class, and Move Method to improve readability, maintainability, and design quality in object‑oriented software.
Clean Codecode smellobject-oriented
0 likes · 19 min read


21CTOOct 7, 2021 · Fundamentals
This tongue‑in‑cheek article lists a series of deliberately bad programming practices—from confusing variable names and deceptive comments to over‑engineered designs and zero testing—to show how to make code virtually impossible to maintain.
Anti-Patterncode smellmaintainability
0 likes · 13 min read


21CTOSep 3, 2021 · Fundamentals
This tongue‑in‑cheek article lists a series of deliberately terrible programming practices—from confusing naming conventions and deceptive documentation to over‑engineered designs and zero testing—showing how to make code virtually impossible to understand, maintain, or debug.
anti‑patternbad practicecode smell
0 likes · 13 min read

This article lists 25 typical code smells such as duplicated code, long methods, large classes, and provides concrete Java examples and refactoring strategies like Extract Method, Extract Class, Move Method, and design recommendations to improve readability, maintainability, and extensibility.
Clean Codebad practicecode smell
0 likes · 23 min read

The article explains why having constructors perform excessive work is a design flaw, describes how to spot this problem through code symptoms, discusses its impact on testability and maintainability, and provides concrete refactoring strategies such as dependency injection, factories, and builder patterns.
Design Principlescode smellconstructor
0 likes · 13 min read

This tongue‑in‑cheek article enumerates a series of deliberately bad programming practices—from confusing naming conventions and deceptive comments to absurd design choices and zero testing—to illustrate how to make code virtually impossible to maintain.
Anti-Patterncode smellmaintainability
0 likes · 13 min read

This article compiles practical Java performance tips—from iterating Map.entrySet() and using Collection.isEmpty() to avoiding magic numbers, hiding utility class constructors, preferring StringBuilder, returning empty collections, and handling enums—helping developers write cleaner, faster, and more maintainable backend code.
Javabackend developmentcode smell
0 likes · 16 min read
