Separation of Concerns
Discussions center on the principle of separation of concerns in software design, including debates over coupling, decoupling, SOLID principles, single responsibility, and OOP architecture pitfalls like 'big ball of mud' or 'loosely coupled spaghetti'.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Because you don't really understand separation of concerns
if that's what you thought separation of concerns meant it's best to forget it
I like the seperation of concerns, do you have an example of conflating these that leads to issues?
Yes. See "decoupling", "big ball of mud".
Sounds like a super example of 'loosely coupled spaghetti'
Author writes tightly coupled architecture, discovers it sucks. So, of course, moans about OOP.
Sounds like somebody figured out the single responsibility principle
Separation of concerns isn't a bad thing
It's called "separation of concerns".
You happily embrace violations of single responsibility?