Procedural vs. Object Oriented Programming (Automated Trading Part 3)

In this video I talk about the difference between Procedural Programming vs. Object-Oriented Programming(OOP) and which one to use for trading applications.

Check out our ONLINE COURSES with discounts over 90% using the links below (~10 Hours each):

[zeuss_]

The only man who puts on a tie in tutorials.
That's my final phase to Subscribing,
😂😂😂😂

I subscribe.
😂😂😂


Jokes aside, this is very good content. 👍👍👍

[julienpilon]

Wow really good job explaining OOP vs procedural, I couldnt really get the difference before this video, you made these concepts so much clearer thanks !

[ensuens]

Your videos are a blessing from the sky for me

[logansegal]

Watching this series now... I really appreciate your teaching style. Very clear and very well explained. Can't wait to continue. Thank you for this!

[FawadZakai]

I’ve been watching PT 1, 2, & 3. Can’t wait to watch the next series.

[ashleycanning]

I think OOP is the way to go with any more complex application design for sure. Compartmentalisation is going to be truely important when refactoring such a system, the ability to create polymorphic types will allow the ability to “bolt on” features and remove them as development progresses and more iterations happen

[indranujhazarika]

Thank You Thank You Thank You !!! Mind blowing explaination. I have been searching for this info for many days. 👍

[caLLLendar]

I keep seeing programmers who are not very experienced with procedural programming attempting to compare it to OOP.

The truth is that you can do similar things with procedural code. You can place the procedural code in functions and namespaces and make it reusable.
It is much faster to *write* procedural code . . .and it is written in the same way we talk.
With OOP, there are typically a lot more lines of code, a lot more files, and eventually technical debt continues to increase.
OOP is best suited for people who are getting paid to work at a job with a boss who doesn't really know what they really want to accomplish.
OOP offers job security.
However, if you're an entrepreneur and a trader, I would say you want to stay away from OOP.
Why?
In part, because everyone is using OOP and using the same indicators and the same technical analysis where 90%+ of active traders FAIL to make a profit (year after year).
If you use the same code and the same concepts, expect to get the same results.

Finally, one of the fundamental purposes of OOP is abstraction . . . meaning "hide the details".
With procedural code (placed in small functions that fit on the screen and separated by namespaces)
you read the code, understand it, and know exactly what is happening and WHERE it is happening.

Notice how the IT industry is moving towards microservices . . . small amounts of code . . . one database . . . and code that looks more and more like procedural code.
That's because when writing a microservice you actually know what the scope of work is and roughly how it will work . . . and the risk of creating technical debt is much lower.

Moreover, if you download and use libraries, they often have a LOT of unnecessary functionality because the framework or library is trying to please everyone.

There are a LOT of drawbacks to OOP, and procedural code can have the same benefits with a competent programmer.
The BEST time to use OOP is . . . when you don't *write* the code at all; Just download enterprise software and use it. :)

[derstreber]

I would have to politely disagree on several points. (in the video, and the comment section in general) OOP techniques do not make your code inherently more reusable than traditional Procedural techniques. In regards to what is said around 6:20, some could argue that OOP is actually worse for reusability on other projects because of how code and data must be glued together to form objects, rather than using structs and procedures where the code and data is apart.

I am glad you mentioned the fact that procedural programming is inherently faster to execute than OOP. ( around 4:26) This, in the majority of any non trivial programs, becomes apparent if you look for it. OOP techniques that continually require the CPU to reload the cache are one of the biggest reasons for this decreased performance because OOP simply does not easily allow for utilizing the hardware to its full potential. And that's without even mentioning SIMD instructions.

Often times I hear it said that OOP is faster for the programmer to write "clean" code or that it is easier to understand complex systems using OOP techniques. Of this too, I am skeptical. I find that strict object hierarchies used for everything throughout the program, simply increases the ratio of "boilerplate code" vs "code that runs". I prefer to debug non boilerplate code.

Personally I think OOP, procedural, functional, DOD, and others (there are more than just 2) can be taken to the extreme and unreasonable dogma can slip in. Also, it is not an all or nothing. There is much overlap "feature" wise. (Also we haven't really defined explicitly what OOP is, it changes depending on who you talk to) For example, you can reuse procedural code, you can even "encapsulate" it should the need arise. From the outside looking in you might think "hey that looks weird", but there may be a reason for it. Is it actually worse?
(If I had to put names on what I am currently using, I'm doing procedural programming, using semantic compression, with a sprinkling of data oriented design and functional programming. No OOP)

In many ways I do think that OOP introduces complexities by adding an artificial code hierarchy. Programming is complicated, and it's just another thing that you need to store in the "cache" of your brain, swapping in and out, while you would like to think about the actual problem at hand. (data manipulation) Maybe it's my low IQ level and lack of education. Perhaps... If so I don't think it unwise to use a programming methodology that does not waste brain cycles when converting thoughts to keystrokes. In short I'm not using OOP.

[macjukej]

I enjoy your videos and your channel
Hope it grows into something great
Good educational value
I have been programming with Python and Lua for FXCM Trading Station Marketscope for almost 2 years now. Fully automated strategies based on a lot of things like support resistance cluster detection etc

[martinp]

Procedural and OOP are paradigms. There are others like functional and imperative.

[dragonhostfx]

I saw your all videos but I unable to understand , I am last 5 year trader in forex, I trade myself but I have no more time to trade so I want a automatic robot please suggest me where I will order it for me which will best. Please suggest me if you can made for me please informed me in my mail I already signup in your site.

[diptipatil]

You are really awesome and geniun person and ur udemy courses also fab just love it👍

[alexpeguero-cruz]

Gang of 4 "Solid Principle Design".

[milkovivaldi]

Object oriented is mql5? Please teach us with a course😁

[coringavinte]

to much complicated using OOP, trading is best done in procedural, you can use functions as objects, that's better