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.
Shotgun Surgery
A single change requires making many small edits across many different classes — a sign of poor cohesion.
2mo ago
quality intermediate
Side Effects
Observable changes a function makes beyond returning a value — modifying global state, I/O, mutation of arguments — that make code harder to reason about.
2mo ago
quality intermediate
Speculative Generality
Unused abstractions, parameters, or hooks added for hypothetical future use that complicate the codebase without present value.
2mo ago
quality intermediate
State Pattern PHP 5.0+
Encapsulates the varying behaviour of an object based on its internal state into separate state objects, eliminating state-based conditionals.
2mo ago
quality intermediate
Strangler Fig Pattern PHP 5.0+ Incrementally replace a legacy system by routing new requests to a new implementation while the old system handles the rest.
2mo ago
quality intermediate
Switch Statement Smell
Repeated switch/if-elseif chains on the same type indicator signal a missing polymorphic design.
2mo ago
quality intermediate
SOLID Principles (Overview) PHP 5.0+
Five object-oriented design principles — SRP, OCP, LSP, ISP, DIP — that together guide towards maintainable, extensible code.
2mo ago
quality intermediate