Treat code smells as questions
Use common OOP code smells as prompts for focused design investigation.
The move: name the smell, then prove the risk. Smells help teams talk about design without vague taste arguments. They are most useful when paired with evidence from change history, tests, and bugs. Large Class asks: are responsibilities mixed? Look for different stakeholders, unrelated method groups, and fixtures that need half the system to create the object. Feature Envy asks: is behavior in the wrong place? A method that reads more data from another object than from itself may belong closer to that data. Shotgun Surgery asks: is one concept scattered? If one policy change touches five files, the concept…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in