Slides from my talk @brainly 12 Mar 2015
Disclaimer: This is my personal vision, based on my knowledge and experience. If you want to challenge it, ask questions, provide feedback and discuss, feel free to ping me on twitter: @waterlink000, I would love to hear from you.
Code examples are in ruby/pseudo-code.
Object Oriented Programming
Most notable features of OOP:
- Encapsulation - keep data together with behavior that needs that data, effectively hiding this data from everything else.
- Inheritance - usually a subclassing, inheriting all behavior and data, in some language even all private details.
- Polymorphism - ability to substitute instances of one class with instances of others.
How important these features are for OO design?
Imagine, that given 100 points you want to distribute them between these 3 features, and each number will represent an importance of corresponding feature.
This would be my answer (and my personal opinion):
And 100 = 80 + 40 + (-20) :)
Why inheritance is so bad?
Because it increases coupling (usually): subclass (usually) depends on some data and/or behavior of its superclass. Even worse: (usually) it is not public data/behavior. I.e.: it violates principle of encapsulation badly. (Usually).
There are actually cases, when you do want your classes to be in inheritance hierarchy, it is the case, when your domain has the same hierarchy naturally in real world. And type inheritance doesn’t really mean behavior inheritance.
So how to avoid violation of encapsulation using inheritance?
- Be careful, use only public interfaces of your superclass.
- Replace inheritance with composition and delegation, because when you use only public interfaces of superclass, then you don’t really need inheritance.
Why coupling is bad?
Imagine you need to change behavior of class X.
You will have to change any other piece of code base, that directly depends on this behavior of class X.
More coupling you have, more changes will have to take place, and probably, in totally unrelated parts of codebase.
As a result it:
- Exponentially increases time required for change
- Invites bugs (lots of)
Dependency, is basically what coupling is, - is not really your friend, so you need to watch out for them.
How to deal with dependencies?
- Dependency inversion principle - Instead of referring foreign system/package/class/module/whatever, refer an abstract interface.
- Dependency injection - Technique, that allows to provision all dependencies to parts of your system and basically fulfill all required interfaces.
1 2 3 4 5
What is the problem with this code? - It is a dependency
Answer -> RatingService. What if you wanted to A/B test different rating models? You will definitely have troubles with that approach, especially if it is not the only place, that reference
Use dependency injection!
1 2 3 4 5 6 7 8 9
Now you can easily have multiple rating services and A/B test them, or do whatever you want, it is really flexible.
It is still coupling
But coupling to abstract interface, instead of real implementation, which means, you can exchange different implementations without changing users of this interface. Which basically improves polymorphism features of your code. It is very loose coupling.
Test Driven Development
How is it related to OO design?
It provides very short feedback on your OO design:
- If you have troubles writing test - your design is wrong and you need to step back
- If you don’t like how your test look like - your design is wrong and you need to step back
- If you have troubles making test green - your design is wrong and you need to step back
It is really almost like pairing partner if used right! Of course pairing still provides even better feedback loop - real-time continuous feedback loop!
Unit tests vs integration tests
Integration tests are scam!:
- Very slow => bad feedback loop
- Exponential count of paths to test
Unit tests just don’t work. Are they?
Everything works in isolation != the whole system works as expected.
Testing in isolation = providing fake objects and/or mocks for all your dependencies
Mocks and fake objects can make your unit test green, but in fact the code is broken, because one of the dependencies has changed its behavior or even public interface in unexpected fashion.
Answer: Cut your system at value boundaries!
Instead of method call boundaries. And we arrive at Actor Model.
Given this example:
1 2 3 4 5
Problems with this class:
- Any user of this class will have to stub out its
#rating_forin unit tests.
- It invites additional behavior to be added (since it is as simple as adding additional public method), which will kill single responsibility feature of this class.
Actor Model solves this
Warning, it is ruby pseudo-code:
1 2 3 4 5 6 7 8
Way better now:
- Allows unit testing easily without mocks and fake objects: by peeking inside its inbox in unit tests instead, and checking that it received right message.
- It is really hard to pack more responsibility to this, since it has no methods, it has just one body, that is responsible for processing exactly one message.
You of course can encode something strange in message, and organize your own method dispatch mechanism through actors inbox, but that is just silly (usually).
Easy to unit test:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
In unit tests you start only one actor - actor under test, and all other actors just get instantiated correctly and passed in as a dependencies where needed. Since they are not started, they will not consume any messages from their inbox, which means that you can consume these inboxes from your unit test, and check that the messages that arrived at inboxes are expected.
When the code is done
- It works!
- It is readable (future me will not curse me for writing this code)
- It has no duplication
- And it is as short as possible (while maintaining all of the above)
Basically a code smell (I’m not talking about documentation comments)
1 2 3
Which is bad from more than one point of view, it literally should have been:
1 2 3 4 5
If code needs comment:
- it is not readable
- it fails to communicate its intent
You should be able to read the code and understand it. In that order: read -> understand.
You shouldn’t interpret it in your head. You shouldn’t have Ruby (or your favorite language here) instance running in your head.
To sum it up
- Inheritance is good only in very rare cases
- Coupling and dependencies are not your friends, take them under control with dependency inversion & injection
- TDD as a shortest feedback cycle for your OO design
- Write code in such way, that you would thank yourself for that in the future
Recommended reading: “Pragmatic Programmer: From Journeyman to Master” by Andrew Hunt and David Thomas. It is insanely good, concise book with lots of awesome references to other resources.
If you have any questions or suggestions, you can always reach me out on twitter @waterlink000.