Thread by @tottinge

so, OO, right?
What people are doing with Java typically is nothing like OO.
Imagine you're creating your own language specific to your problem domain and solution domain.
That's a beginning.
A language in which you can solve your problems in your domain and stack.

It doesn't exist, btw. Java, JS, Python, C#, Smalltalk -- they're not it. They're the language you build your language in. You don't implement the solution in Java. You implement your solution in the language you've built in Java.

The problem is that you have two locations in space, a bunch of roads, and you want to route a path from one place to the other.
Don't do that in ints, strings, functions, and doubles.
Do it in places, paths, and routes.

And, of course, some verbs go with some nouns and not with others. Imagine modules with a data structure and a bunch of functions that operate on the structure - see how that's nouns and verbs, kinda, if you squint?

Now it's not exactly that, and it's not entirely that, and it's not that only. It's a first approximation - a language you develop that describes the space and how you solve problems.

You grow the language and connect the ideas, and patterns of behavior occur, and some structures become more obviously beneficial than others.

Sure, sometimes the right way to think about the domain isn't the best way to implement it. There may be efficiencies to consider.
And there is always integration with libraries and stuff.
But, hey, the idea is that you don't have to build your huge system with java primitives.

Now, there is an important point here: you can’t stop, design and build a perfect language, and then use it to solve problems.

Language is organic and grown.

You must speak it while making it, and make it while speaking it.
It grows with your understandings.

You know how you sometimes realize something new and wish there was a word for it? That’s an OO thing as well as a spoken language.
You will discover and invent many things.