Code Smells and Anti-Patterns Cheat Sheet

Updated 2026-03-18

Next Topic: Concurrency and Parallel Programming Patterns Cheat Sheet

Code smells are surface indicators that suggest deeper design problems in software systems — they're not bugs, but warning signs of maintainability issues, technical debt, and architectural decay. First coined by Kent Beck and popularized by Martin Fowler, these patterns help developers identify when code needs refactoring. Anti-patterns, by contrast, are common solutions that initially appear reasonable but lead to negative consequences — often arising from organizational pressures, misapplied design patterns, or lack of understanding. The key insight: both code smells and anti-patterns are symptoms, not diseases — they point to underlying structural problems that, if addressed early, prevent systems from becoming unmaintainable legacy codebases.

What This Cheat Sheet Covers

This topic spans 11 focused tables and 58 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Fowler's Bloater Code SmellsTable 2: Fowler's Object-Orientation Abuser Code SmellsTable 3: Fowler's Change Preventer Code SmellsTable 4: Fowler's Coupler Code SmellsTable 5: Fowler's Dispensable Code SmellsTable 6: Additional Code SmellsTable 7: Architectural Anti-PatternsTable 8: Development Process Anti-PatternsTable 9: Code Organization Anti-PatternsTable 10: Code Smell Detection & RemediationTable 11: Detection Tools & Technologies

Table 1: Fowler's Bloater Code Smells

Smell	Example	Description
Long Method	`def processOrder():` `# 200 lines of code` `# mixing validation, calculation,` `# database access, logging...`	• Method exceeds 10-15 lines and does too many things • harder to understand, test, and reuse.
Large Class (God Class)	`class OrderManager:` `# 50 fields` `# 100+ methods` `# handles orders, payments,` `# shipping, inventory...`	• Class has too many responsibilities and fields • violates Single Responsibility Principle.
Long Parameter List	`createUser(name, email, age,` `addr, city, zip, country,` `phone, fax, company)`	• More than 3-4 parameters make methods hard to call and understand • often signals missing object abstraction.

Table 1: Fowler's Bloater Code Smells

Smell	Example	Description
Long Method	`def processOrder():` `# 200 lines of code` `# mixing validation, calculation,` `# database access, logging...`	• Method exceeds 10-15 lines and does too many things • harder to understand, test, and reuse.
Large Class (God Class)	`class OrderManager:` `# 50 fields` `# 100+ methods` `# handles orders, payments,` `# shipping, inventory...`	• Class has too many responsibilities and fields • violates Single Responsibility Principle.
Long Parameter List	`createUser(name, email, age,` `addr, city, zip, country,` `phone, fax, company)`	• More than 3-4 parameters make methods hard to call and understand • often signals missing object abstraction.