Tidbits tagged with #oop (11)
You want to learn with really good examples why all inheritance is bad, and why you should think twice if you want to inherit in places or if you jump on the ship with the new tool/library/framework that forces you to inherit from it's base class. Watch the first 30 minutes https://vimeo.com/163860086 (exactly until 30:00).
Continue reading →
If I tell you who gave the answer you will run off and read it, so I don't and expect you to be interested enough in following the link to the answer.
Continue reading →
Wikipedia says about cohesion, it refers to the degree to which the elements of a module belong together.
And about coupling it says how closely connected two routines or modules are.
Continue reading →
On the famous c2 wiki find "Alan Kay On Messaging". His words are from the year 1998 and still so true. And I am only close to the beginning of really understanding. But I have to, as usual, extract some of the key points for me. Make sure to read the entire message anyways, it's really very short!
Continue reading →
I have been titled as a Sandi Metz fanboy, I am :). I use "send to" and "plays the role" since I read her book poodr.
Continue reading →
Pharo - object-oriented programming language and a powerful environment
Continue reading →
Another pearl by @KevlinHenney in his Functional Programming You Already Know
is his explaination of why we actually should leave out prefixes to our functions, such as get
and set
.
Continue reading →
Links about naming things
Continue reading →
Linked in the comments of this I found another great article, which I just have to quote.
Continue reading →
I was about to write a "Handler" class. But I remembered that the "er" classes are not so good.
Continue reading →
Refactor to functional
Continue reading →