|
|
|
|
|
|
by davidmurdoch
1093 days ago
|
|
|
The intro has nothing to do with the rest of the article, really. The author claims it does at the end, but it's just trashing OOP for fun (the author even says this). OOP is fine. And DRY (what the core idea of the article is getting at) applies in OOP paradigms as much any another. The arguments the author makes are orthogonal to OOP. The author seems to not enjoy planning before writing code, which I guess is more necessary for OOP than other paradigms? |
|
|
Or the author's experience (which is extensive) has led to the conclusion that all that planning you want to do at the beginning rarely gets you the proper abstractions.