Discover and read the best of Twitter Threads about #CodeSmells
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
I’m creating a thread on #softwaredesing. One tip per day.
Until no advices are left or I reach thread limit. Whatever happens in the first time.
Until no advices are left or I reach thread limit. Whatever happens in the first time.
Tip 01: Do not subclassify concrete classes.
Tip 02: Variable names should indicate role. Never type
