Download to read offline
Uploaded byVincent Vauban
👃🤢 7 CODE SMELL: spot ’em fast, fix ’em faster
I turned my latest clean-code notes into a short LinkedIn carousel you can save and share. Each slide hits why it’s bad + how to fix it—no fluff. (Titles are clickable for the deep-dive articles.) What’s inside ⬇️ • Middle Man 👤→ Cut pass-through layers, reduce coupling • Long Parameter List 📏→ Wrap into a value object, ditch flags • Knowledge Duplication 📝📝→ Extract helpers, reuse wisely • Primitive Obsession 😱→ Model rich types, centralize validation • Speculative Generality 🔮→ Delete unused stuff, build for today • Long Method → Extract responsibilities, name for intent • Feature Envy 😋→ Move behavior where the data lives 👉 Swipe through, save 🔖 for code reviews, and drop a comment: Which smell bites you the most lately? #CleanCode #Refactoring #SoftwareCraftsmanship #CodeSmells #DeveloperTips #SOLID #Maintainability #TechDebt #Java #Programming
More Related Content
Similar to 👃🤢 7 CODE SMELL: spot ’em fast, fix ’em faster
👃🤢 7 CODE SMELL: spot ’em fast, fix ’em faster
- 1. Code Smells Why they’rebad & how to fix them September 2025
- 2. CODE SMELL: Middleman 👤👨👤 • Why is it bad? – Adds no value—just delegates calls. – Increases coupling across interfaces. – Gives a false sense of information hiding. – Shallow methods hint at poor structure. • How to fix it? – Remove pass‑through layers with no added logic. – Keep layering but avoid ‘just forwarding’ layers. – Combine methods and simplify the class interface.
- 3. CODE SMELL: Thelong parameter list 📏 • Why is it bad? – Hard to understand and maintain. – Ordering mistakes easily break calls. – Flags (boolean/enum) hide intent and paths. – Optionality becomes messy as lists grow. • How to fix it? – Replace many params with one data object. – Derive values—remove redundant parameters. – Avoid flag parameters; split variants into functions. • (Title links to details)
- 4. CODE SMELL: Knowledgeduplication 📝📝 • Why is it bad? – Every change requires hunting all copies. – Duplicates drift and behave inconsistently over time. – Couples unrelated places to the same changing knowledge. • How to fix it? – Extract shared knowledge into helpers/types. – Reuse them consistently—keep them small and SOLID. – Do not merge code that represents different knowledge.
- 5. CODE SMELL: Primitiveobsession 😱 • Why is it bad? – Poor encapsulation; logic scattered across code. – Validation and operations get duplicated. – Easy to forget updates when behavior changes. • How to fix it? – Model domain concepts with rich types. – Avoid type explosion—seek better abstractions. – Centralize validation and behavior in those types.
- 6. CODE SMELL: Speculativegenerality 🔮 • Why is it bad? – Unused fields/methods/classes add complexity. – Over‑engineering wastes time and attention. – Harder to maintain and onboard. • How to fix it? – Remove unused params, overloads, and types. – Keep structure simple; build for today’s use case. – Add generality only when real needs emerge.
- 7. CODE SMELL: Longmethod • Why is it bad? – Multiple responsibilities tangled together. – Harder to reason about and to change safely. – Buried knowledge cannot be reused. • How to fix it? – Identify the core purpose; extract the rest. – Name functions well to convey intent. – Create small, cohesive helpers.
- 8. CODE SMELL: FeatureEnvy 😋 • Why is it bad? – Low cohesion leads to high coupling between modules. – Easy to call things in the wrong order—bug‑prone. – Boundaries are blurry; responsibilities unclear. • How to fix it? – Move the behavior to the data it uses most. – Redraw boundaries to improve cohesion. – “Put things together that change together.”
- 9.