Quality terms
Because working code and good code are not the same thing
Code that works today but cannot be understood, tested, or modified tomorrow is a liability, not an asset. Code quality covers metrics, static analysis, design principles like SOLID and DRY, refactoring techniques, and the habits that separate codebases teams love from ones they dread maintaining. Good quality is not about perfection — it is about making the next change easier than the last.
Inline Temp Variable Refactoring
Inline Temp removes a temporary variable used only once when its name adds no clarity — replacing the variable reference with its expression directly.
2mo ago
quality beginner
IoC Container PHP 7.0+
An Inversion of Control container automatically resolves and injects class dependencies — you declare what a class needs, the container figures out how to create it, eliminating manual dependency wiring.
2mo ago
quality intermediate
Interpreter Pattern
A grammar represented as a class hierarchy — used for search query parsers, expression evaluators, and rule engines.
2mo ago
quality advanced
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
Interface Segregation Principle
Clients should not be forced to depend on interfaces they do not use — prefer many small, focused interfaces over one large one.
2mo ago
quality intermediate
Iterator Pattern PHP 5.0+
Provides a uniform way to traverse a collection without exposing its internal structure — the foundation of PHP's foreach and SPL iterators.
2mo ago
quality intermediate
Immutability PHP 8.1+
Objects whose state cannot change after construction — immutable objects are inherently thread-safe, predictable, and easy to reason about.
2mo ago
quality intermediate