Discover and read the best of Twitter Threads about #dependencyinjection
Most recents (2)
#CodeSmell 01: Your objects are a bunch of public attributes
Problem: en.wikipedia.org/wiki/Anemic_do…
Solutions:
1) Find Responsibilities.
2) Protect your attributes.
3) Hide implementations
4) Delegate
Problem: en.wikipedia.org/wiki/Anemic_do…
Solutions:
1) Find Responsibilities.
2) Protect your attributes.
3) Hide implementations
4) Delegate
#CodeSmell 02: Code has lots of comments
Problem: Comments are coupled to implementation
Solutions:
1) Refactor methods
2) Rename methods to more declarative unes
3) break methods
4) If a comment describe what a method does. Just name the method with this description
Problem: Comments are coupled to implementation
Solutions:
1) Refactor methods
2) Rename methods to more declarative unes
3) break methods
4) If a comment describe what a method does. Just name the method with this description
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
