2 ms·
The onion anti-pattern is Separation of Concerns taken as mythology, not practicality. A reasonable way to OOP is: 1. Understand your domain and work hard to m
by TheOtherHobbes 6y ago
The onion anti-pattern is Separation of Concerns taken as mythology, not practicality.
A reasonable way to OOP is: 1. Understand your domain and work hard to match its structures. 2. Delegate and separate where there's an unquestionable benefit, not for the sake of it. 3. Likewise for inheritance hierarchies. 4. Don't create entities unnecessarily.
Every single decision should have a clear practical rationale. SOLID on its own is not a rationale - it's a guide, but to use it you need to understand what a concern is from the domain POV, not from the code POV.