A catalog of frequent coding mistakes that inflate complexity. For each anti-pattern, the page explains why it harms maintainability and how to replace it with lean alternatives.
Editorial note
Lean, accessible coding wisdom inspired by clean-code storytelling. Think of this as a glossy guide to pare down the noise without losing nuance.
Anti-patterns are the sirens of software development—clever at first glance, but when followed, they lead teams into tangled, hard-to-maintain code. This page treats each misstep as a learning moment, offering lean, practical remedies that align with a culture of clarity and craftsmanship.
In the spirit of Fat Free Code, we celebrate lean thinking: identify bloat, name it, and replace it with disciplined, readable patterns. Below are common pitfalls illustrated with real-world intuition and actionable fixes.
When one class or module grabs everything, it becomes a monolith that’s hard to test and reason about.
Lean fix: break responsibilities into cohesive units, favor small, focused functions, and define clear interfaces that reduce cross-cutting concerns.
A tangle of interdependent paths makes changes risky and unpredictable.
Lean fix: introduce modular boundaries, explicit dependencies, and gradual refactoring to reduce hidden couplings.
Adding layers of abstraction without concrete need slows progress and overwhelms teammates.
Lean fix: implement the simplest viable solution, then evolve with feedback and incremental improvements.
Optimizing for unseen bottlenecks can waste time and obscure readability.
Lean fix: profile with intent, target real bottlenecks, and keep correctness primary. Optimize with purpose, not paranoia.
Pull responsibilities into well-named helpers or modules.明确 interfaces reduce cognitive load and make future changes safer.
Define clear input/output contracts, so teams can reason about behavior without following a maze of dependencies.
Meaningful names reveal intent, reduce the need for comments, and improve team onboarding.
Build confidence with focused tests that verify behavior, not incidental implementation details.
Explore more on the Fat Free Code hub: