Hit-parade of clean code violations
summary
Survey of 15 common clean‑code violations found across many code reviews, ranked by frequency and impact, with concrete fixes to apply during review: stop noise like magic imports, eliminate returning nulls in APIs in favor of empty collections or Optionals, break up long methods and remove duplicated logic, fix hidden side effects and poor exception handling, enforce module boundaries to avoid cyclic dependencies, and write fast, independent, meaningful tests so refactors become safe.
AI-written summary · about
chapters (18)
- 0:00Introduction to clean code
- 2:12Code review best practices
- 4:59Unused imports issue
- 6:03Bad class naming examples
- 7:30Module decomposition problems
- 9:20Dead code and unused features
- 10:46Poor exception handling
- 11:49Useless code comments
- 18:36Inconsistent coding style
- 22:50Slow and flaky tests
- 26:44Side effects in functions
- 29:55Too many function arguments
- 32:41Long methods harm readability
- 35:16Null checks and optionals
- 39:10Bad naming conventions
- 41:18Single responsibility principle
- 44:29Code duplication dangers
- 45:11Conclusion and key takeaways
