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.
Reducing Cyclomatic Complexity Techniques
Cyclomatic complexity counts independent code paths — reduce it by early returns, extracting conditions to named functions, using lookup tables, and replacing switch/if chains with polymorphism.
2mo ago
quality intermediate
Refactoring Boolean Flag Parameters
Boolean flags as function parameters obscure intent — replace with enums, separate functions, or named options objects for self-documenting APIs.
2mo ago
quality intermediate
Replace Magic Literal with Symbolic Constant
Magic literals (numbers/strings hardcoded without context) should become named constants — MAX_RETRIES = 3 is self-documenting; the literal 3 is not.
2mo ago
quality beginner
Refused Bequest
A subclass that inherits methods it doesn't need or want, signalling a misused inheritance relationship.
2mo ago
quality intermediate