The Art Of Object Oriented Programming

Throughout the video, we'll explore essential OOP concepts such as classes, objects, inheritance, abstraction, polymorphism, and encapsulation, demonstrating how they enable us to create modular, reusable, and extensible code.

You'll witness how OOP encourages a holistic and structured approach to problem-solving, empowering developers to build complex systems while prioritizing maintainability and scalability (In Theory).

Timecodes
0:00 - Intro
2:20 - Classes
4:26 - Constructors
5:23 - The Four Principles
5:53 - Inheritance
7:30 - Abstraction
8:33 - Polymorphism
9:37 - Encapsulation
11:00 - Conclusion

[baka_baca]

Ahh OOP, a paradigm for making simple problems extremely complicated and painful. I have 4 years of experience with OOP for web development in a professional setting in multiple languages, dozens of codebases, and across many teams. I'm still waiting for a time where OOP truly made my job easier, the only times I thought it might have made my life easier just ended up being features of strongly typed languages or compiled languages. Learn OOP so you can understand it when you come across it and so you can understand why you should avoid it whenever you reasonably can.

[yashganar]

bruh I thought this channel had 1M or something subscribers, you are about to blow with this content!, kudos for the future! you made me understand in 15 mins what the university teachers take 5 hrs to understand

[commentvsreply]

I just found your 'art of programming' video now I'm here.. This is great content and you seem to have a knack for it! Good luck sir, I'll be waiting for you to get 100k subs 👏

[ChaosArtist]

Nice explanation of OOP, I'm continually having to wrap my head around the details of each programming paradigm and the pros and cons of each. Looking forward to seeing more of your videos.

[VPSOUNDS]

This was so good that i felt the need to pay you for all that well put info.

[davidkik]

Great job explaining the impossible. I've listened to many tutorial & yours are amazingly simple to understand. Keep them comming 🤜🏻💥🤛🏻

[smanzoli]

OOP should be used when many people in a team are cooperating to write huge and complex programs... and when most of the team do prefer OOP.

[mastershonobi]

Great explanation and vid; keep them
Coming……🔥🔥🙏🏾🙌🏿

[valentinussofa]

I subscribed your channel. It seems I have become your fan. Keep working bro. I'm sure your YouTube channel will grow rapidly. I will help promote your channel for OOP programmers. Many thanks from Indonesia.🙏

[nuwagabaprinceaubrey]

I Love the music in the background, where can I get it

[filipg]

OOP exists so that you can have a failed paradigm to compare against, it's a case study, like Enron of software industry.

[principleshipcoleoid]

6:16 wouldn't Rust's Animal trait be somewhat useful? So we get composition over inheritence.

[gJonii]

Inheritance, a mistake every modern programmer has to make in their path to realizing OOP sucks.

[MrAbrazildo]

5:45 and 10:23, by here C++ starts to be better than Java: public modifier/setter is not a good thing, although supported. In C++ you can elect a few f()s to change private content, with or without a modifier. This is the actual encapsulation. It seems Java hasn't something alike.

[nmpaczek]

OOP is about messaging, not objects. C language isn't OOP but u still can do the same as u mention:
struct character
{
int height;
int attack;
int defense;
};

[rivierasperduto]

Why getters and setters and not mutators and accessors? You use a lot of correct terminology and then you forgot this one? Overall though I really liked your video you are good at explaining.

[TheDavilaramiro]

I all depends on how your brain is hard-wired... or how can you be able to re-wire it yourself.

[Tony-dprl]

OOP was the worst thing to happen to software development. Regardless of the intent. If we had gone down a different path we would be decades ahead of where we are now. The joining of Code and Data together was just a fundamentally bad idea, laced with the even worse concepts of Inheritance and Polymorphism. It was the software engineering version of the Imperial Measurement System.

[AURORAFIELDS]

I'm not sure why in god's name you thought you need severe code duplication to set the *same* variables for different entities if you don't have classes. Arrays and structs exist in C, and any intermediate programmer will figure out how to use pointer or indices to set different variables of the same type with a single function. If you're gonna argue for why OOP is good, please don't post something so offensively misinformed.