Symptom
A class with too many fields and methods — multiple unrelated responsibilities under one type.
Goal
Each class has one cohesive purpose; methods cluster around fields they actually use.
Smellier version
class Order {
// lineItems, totals, customer info, shipping address, audit log, ...
}class Order { /* lineItems, totals */ }
class Customer { /* name, email */ }
class Shipping { /* address, track */ }Savings
Smaller, more testable units; clearer ownership; faster reading.
Note
Cognitive load: every reader pays for fields they don't care about; merge conflicts spike; testing is unfocused.