Object Oriented Programming is an expensive disaster which must end

I run into this when I go to a job interview. It does not matter if I interview for a Ruby job, or a Java job, or a PHP job, the job interviewers ask me if I know what OOP is. They ask me to define “encapsulation” and “polymorphic dispatch”. These are standard questions, to which I am expected to give the standard answers. And when they ask me “What are the benefits of OOP?” I find myself wanting to give an awkwardly long answer, which consists “These are the 12 things that are supposed to be the benefits of OOP, but really OOP has no unique strengths.” And so I am writing this essay, and in the future, when I’m asked questions like this at a job interview, I’ll simply directly people to what I have written here.

#interfacesmieci
#java #csharp #ruby #php #scala

Postanowilem porzucic rakotworze tagi programowanie i informatyka na rzecz innych, mniejszych, bardziej specyficznych tagow.

Drugi podobny artykul - Programming without objects