A demonstration that inheritance is a good technique. Which it is not. It hurts locality of behaviour, and that's bad because it increases the rate of mistakes. There have been studies about this.
A demonstration that inheritance is a good technique. Which it is not. It hurts locality of behaviour, and that's bad because it increases the rate of mistakes. There have been studies about this.
As for studies, I'd be interested to read those, as most studies of developer productivity I've seen aren't that good.
Anyway, I don’t care about what we should mean by this and that. What I do care about is whether inheritance is useful or not. And so far, I have seen no evidence that it is anything more than highly situational — meaning, doesn’t have a better alternative for almost everything.
The study I recall didn’t measure productivity, it counted bugs.
Anyway, I spent enough time on the subject to close the case. Until I stumble upon cogent evidence to the contrary, inheritance is not worth my time. I won’t use it, I will steer my colleagues away from it, and I will quit gigs that use it too heavily.
Broader question (much broader): Do you know of any place that has a good collection of studies that answer questions like this (questions about CS, language design, and such)?