Object-oriented programming

We're changing our architecture every three or four months because the world is changing, and we need to adapt ourselves to this new technology.

So it's like everything is new all the time, right? And this is very different from, you know, 20 years ago when I was learning programming and like getting, and like this understanding and like OOP and functional programming and systems architecture, and like everything was like you got that knowledge and, and, and you took it with you wherever you went.

And like nowadays, everything is completely different.

So I don't care if they come with AI experience.

Like, I wanted to work with people who knew things in the detail.

But I understand now as a CTO, uh, who's, you know, looking to connect technology with the business and provide the business value and outcomes that, you know, times have changed.

And now natural language is becoming our programming language the same way we used to do assembly and then we got to OOP and abstractions on top of that.

We're now at this higher level of abstraction.

Every time you write a class, ask How many places break if this changes? The lower that number, the better the design.

Common OOP design mistakes.

The God object.

One massive class that accumulates everything.

Practical, testable and boring in exactly the right way.

Conclusion.

OOP is a design mindset.

OOP doesn't begin with syntax and end with four terms.

You know,

everyone uses classes, objects, even if they're not big OOP folks, you still create objects.

I mean, do you have a number? You know what I

mean? Well, it's just, and it's convenient, but I think if you were, again, performance debugging and triaging and you ran into this, you've been surprised.

Which brings us to the core philosophy of Java.

Object-oriented programming, or OOP.

OOP fundamentally flips that old spaghetti code paradigm on its head.

Instead of code acting on data, OOP is organized around the data itself.

The core principle is that the data controls access to the code.

But how does it actually do that?

OK, I have to stop you, though.

I'm looking at all these classes, these strict hierarchies, these heavily guarded black boxes.