> At the end of the day, for general programming, any paradigm is going to end up producing similar quality of code. Developer competence I'd say that "pure" p

> At the end of the day, for general programming, any paradigm is going to end up producing similar quality of code. Developer competence I'd say that "pure" paradigms tend to be almost equally bad (tried functional programming in production code, wasn't all it's advertised to be). But this actually leaves you with more freedom, because you have to pick pieces and create your own style. So it turns out to be more important, not less, that you understand the how and why of each paradigm. As for how good this particular article was - well, I agree with the premise and it gives links to sources. May not be the Mona Lisa of articles, but it got my upvote. I'm not a regular HN reader so it's the first article on this topic I've seen in a while.