Use Design Patterns and SOLID to program without if tests

A full hands on example of how we can use SOLID principles and good Object Oriented Design to write a program without if tests. This makes for a flexible and maintainable program, built with best practices.

In this video, I do a complete hands-on example that demonstrates the Command and Factory patterns. I also discuss each of the SOLID principles, and how they can be used to write better code:
Single Responsibility
Open Closed Principle
Liskov Substitution
Interface Segregation
Dependency Inversion

[hamzaarras]

This video helped me a lot!. I made clean and flexible code while working on an android project, thank you Mr. Brandan Jones

[hubstrangers]

Thank in a combination substance with time stamp!!!....

[ExploraByte]

Thanks a lot for these valuable content !

[СергейБулкин-юъ]

Brandan, since it's an unusually long video - please put Chapters on it. Youtube allows to generate those automatically.

[dsaif]

Thank you for the content
But I think the code in the github repo provided in the description is not the same as in the video

[ansismaleckis]

I was expecting at least a 10 inch beard at the end of this video since it is 45 mins. Anyways, great content! I am self-thought coder and I got my first programming job (mostly in java) just a couple a months ago. Even though I work in Java I am a bit sceptical about OOP and SOLID but this example demonstrates that these concepts can be valuable in certain scenarious.
I would be curious to hear from Mr. Brandan Jones opinion on procedural programming in java.
The example presented here could be rewritten with procedural approach (even in java) with fewer files, fewer classes and fewer lines of code. Instead of three classes implementing an interface there could be just three execute functions/methods and in place of an object factory there could be just a simple function/method that selects one of the three execute methods based on a filename. So where/when does the OOP provide advantage over procedural approach? I understand that in a trivial example like this one the OOP advantages are not obvious. I am curious about scenarious (likely a lot more complex) where the OOP has the advantage over procedural approach.

[kaatlev]

spoiler alert: the man grew an entire mustache and chops at minute 9..okay back to the content.

[retohummer]

Sorry, couldn't concentrate on the content of the video ... never saw a developer in a suit and tie 🤣🤣🤣