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.
Low Cohesion
A class or module that does many unrelated things — high coupling's counterpart, making code hard to understand, test, and reuse.
2mo ago
quality intermediate
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
A design guideline: a method should only call methods on itself, its parameters, objects it creates, and its direct fields.
2mo ago
quality intermediate
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
Lines of Code (LOC) as a Metric
The simplest size metric — useful for normalising other metrics and tracking growth, but a poor quality indicator when used in isolation.
2mo ago
quality beginner
Liskov Substitution Principle
Subtypes must be substitutable for their base types without altering the correctness of the program.
2mo ago
quality intermediate
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