Tag: code-smell
🤖 AI Guestbook — #code-smell educational data only
|
|
Last 30 days
Agents 25
Amazonbot 7Perplexity 4
Perplexity 2Amazonbot 2
Amazonbot 217Perplexity 129Ahrefs 78Google 58Unknown AI 57ChatGPT 33Claude 16Majestic 16SEMrush 14Bing 1DuckDuckGo 1
Most referenced — #code-smell
Long Method 4Magic Number 2Magic Strings 2Deep Nesting 2Primitive Obsession 2Temporary Field 2Middle Man 2Comments as Code Smell 1
How they use it
crawler 574
crawler_json 33
pre-tracking 13
Tag total620 pings
Terms pinged27 / 27
Distinct agents10
Error Suppression Operator (@) PHP 5.0+
Prefixing a PHP expression with @ silently suppresses all errors and warnings it generates — hiding bugs instead of handling them.
2mo ago
quality beginner
Boolean Parameters (Flag Arguments Smell)
A boolean parameter that switches a function between two different behaviours — a sign the function should be split into two.
2mo ago
style beginner
Comments as Code Smell
Excessive or explanatory comments often indicate that the code itself is too complex or poorly named to be self-explanatory.
2mo ago
quality beginner
Data Clump
The same group of variables appearing together repeatedly — a signal they belong in a class together.
2mo ago
quality intermediate
Deep Nesting PHP 5.0+
Code indented 3+ levels deep — guard clauses and early returns can flatten most deep nesting.
2mo ago
style beginner
Divergent Change
One class changes for many different reasons — a sign it has too many responsibilities.
2mo ago
quality intermediate
Duplicate Code PHP 5.0+
Identical or near-identical blocks of code in multiple places — the most common source of maintenance bugs.
2mo ago
quality beginner
Feature Envy PHP 5.0+
A method that accesses the data of another class more than its own — suggesting it belongs in that other class.
2mo ago
quality intermediate
God Class PHP 5.0+
A class that knows too much and does too much — violating the Single Responsibility Principle.
2mo ago
quality intermediate
Inappropriate Intimacy
Two classes that access each other's private fields and internals too freely, creating tight bidirectional coupling.
2mo ago
quality intermediate
Inconsistent Names Smell
Using different terms for the same concept across a codebase — fetchUser vs getUser vs loadUser — increases cognitive load and obscures relationships.
2mo ago
quality beginner
Large Class
A class that has grown to accumulate too many responsibilities, fields, and methods — a sign it should be split into focused, cohesive classes.
2mo ago
quality beginner
Law of Demeter — PHP Examples
The Law of Demeter (don't talk to strangers) limits method chains — each unit should call only its direct collaborators, not traverse object graphs.
2mo ago
quality intermediate
Lazy Class
A class that doesn't do enough to justify its existence — the cost of understanding it exceeds the value it provides.
2mo ago
quality beginner
Long Method PHP 5.0+
A function or method that is too long to understand in one reading — typically 20+ lines is a signal to split.
2mo ago
quality beginner
Long Parameter List
A function or method with too many parameters — typically 4+ — making calls hard to read and easy to get wrong.
2mo ago
quality beginner
Magic Strings
Raw string literals used directly in code as identifiers or flags — prone to typos, hard to refactor, and lacking IDE support.
2mo ago
style beginner
Message Chains
A long chain of method calls ($a->getB()->getC()->getD()) that tightly couples code to the internal structure of multiple objects.
2mo ago
quality intermediate
Middle Man
A class that does little more than delegate every method to another object — an unnecessary layer of indirection.
2mo ago
quality intermediate
Parallel Inheritance Hierarchies
Every time you create a subclass of one class, you must also create a corresponding subclass of another — a sign of entangled designs.
2mo ago
quality intermediate