[x0hm]

Every once in a while I see this article, and every once in a while I fear that junior programmers are going to read it as if it is at all accurate.

This is a great article that represents the fundamental problem of OOP - that developers don't actually use it.

Instead, we have a lot of procedural programmers writing code that masquerades itself as "object oriented", when in reality it's imperative functional decomposition that we're calling OOP because we don't know any better.