to get to the clearest design, it's ok always be shifting things (methods, values, entities, aggregates) to where they make the most sense in the model; reflect on ISP, cohesion, coupling, on adding/removing layers, on simplicity, on asking more questions
spoken like a true refactor addict
where would be the best home for a piece of logic?
a) in the object that knows the business rules
b) in the object that has the data
a) in the object that knows the business rules
b) in the object that has the data
there might be another option:
c) in the object that has the data, and is injected with the rules (in a Strategy), by the object that knows the rules
#ddDesign #strategyPattern #dependencyInjection
c) in the object that has the data, and is injected with the rules (in a Strategy), by the object that knows the rules
#ddDesign #strategyPattern #dependencyInjection
• • •
Missing some Tweet in this thread? You can try to
force a refresh
