Timeline for Avoiding the Anaemic Domain - How to decide what single responsibility a class has
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2018 at 1:26 | comment | added | Andy | Anemic has to do with the class not having behavior. Your example shows no behavior whatsoever; that class is just a data container.. which is fine if that's its responsibility. The problem with anemic models is that you really aren't doing OOP (which is behavior + data), you're doing procedural programming (passing data structures to functions). | |
| Jun 26, 2013 at 14:31 | answer | added | Karl Bielefeldt | timeline score: 1 | |
| Jun 26, 2013 at 13:37 | vote | accept | SeeNoWeevil | ||
| Jun 26, 2013 at 13:20 | answer | added | guillaume31 | timeline score: 5 | |
| Jun 26, 2013 at 10:39 | comment | added | SeeNoWeevil | I wanted to clarify. I think people are getting hung up on my particular example and if it does/does not contain more than a single responsibility. Assume that I have a class which requires multiple operations that are definitely separate responsibilities (reasons to change) but are all conceptually similar. How do I decide which single responsibility belongs in the class and which go elsewhere? I'm starting to feel like the answer is.. it doesn't matter. Pick one. | |
| Jun 26, 2013 at 10:33 | answer | added | Euphoric | timeline score: 1 | |
| Jun 26, 2013 at 10:28 | answer | added | Useless | timeline score: 3 | |
| Jun 26, 2013 at 9:42 | answer | added | Michael Borgwardt | timeline score: 2 | |
| Jun 26, 2013 at 9:26 | history | asked | SeeNoWeevil | CC BY-SA 3.0 |