(author here) Thanks for pointing this out, you're right that Loan would most likely be a POJO with other surrounding helper abstractions. Might rework this cod

(author here) Thanks for pointing this out, you're right that Loan would most likely be a POJO with other surrounding helper abstractions. Might rework this code example a bit so it's a fairer comparison. The point I was trying to convey is not that OOP is bad, it's just a tool after all and some codebases can be great, but rather there are multiple ways to structure and write code that come with different trade-offs (FP is another obvious example). Many developers don't bother to understand these tradeoffs and go deeper and deeper down the abstraction rabbit hole to the point it becomes harmful, without questioning what value they are actually getting from it, think FizzBuzzEnterpriseEdition. Stripe realized most devs were writing code to be executed in a "lambda style" way and optimized the experience for that via Commands, which I thought was cool. I phrased it as "The OOP Myth" since I've only seen large companies follow OOP so it _was_ pretty shocking to me to see this in action.