Uploaded December 2016 | Updated September 2026, 3 weeks ago
Being in the programming mindset is very important for new programmers. I’ve wasted countless hours listening to experts talk about OOP verses procedural and how one is much better than the other. I found out both where right and you maybe wondering how that’s possible. Well it’s possible because sometimes procedural is better and sometimes OOP is better for the job and by combining both styles you can benefit.
To understand both paradigms and how they work in parallel, look at the way your mind works. For example firstly it's procedural; it’s functionally looking around the room thinking of what it's going to do next. This is procedural, it's not working with any objects specifically but it's analysing data which may or may not include objects. Now you've gone through the procedures of looking around the room and decided you want to watch the television.
Now we can work with objects so we shift from the procedural paradigm to the OOP paradigm. Now our mind is in the OOP paradigm for our television object; so we can work with this object easily. Then when we’ve turned the television on, we need to go back to procedural again by making a choice of what program to watch. So now we switch back into procedural mode to think logically about what we want to watch; we're in effect analysing channel data to find what we’re looking for.
You can see by mapping out our minds in the real world we can understand multi paradigm programming with procedural and OOP by observing the shift that occurs. This'll help when building large scale applications that require the ability to implore both of these paradigms to build apps extremely quickly.
When considering analysis could take hours, days, months or even longer it shows procedural is supposed to be harder. It’s slower and can be more difficult depending on the task. However when the analysis is finished we can now decide what object to work with. Our world consists purely of objects so whenever we do something in the real world we’re in the OOP paradigm; wether it’s a television, cooker, lawn mower or any other object type.
Consider also the OOP paradigm is simpler when working with object types. For example we can work with the television type object. It maybe your television or you're friends, however because we have general understanding this television type object, identifying its purpose, we can easily work with that object type. Yes they can differ and they're unique; but regardless the type of object has familiarity with us naturally so it's supposed to be easier in this paradigm when working with objects but not analysis which is procedural and is more difficult sometimes.
Programming 101 course:
youtube.com/playlist?list=PLGC-hHIh7l5s6Spz86OT1u0A7kvQH-2B0
This tutorial is brought to you by avelx.co.uk - Coding tutorials to help you grow.
Being in the programming mindset is very important for new programmers. I’ve wasted countless hours listening to experts talk about OOP verses procedural and how one is much better than the other. I found out both where right and you maybe wondering how that’s possible. Well it’s possible because sometimes procedural is better and sometimes OOP is better for the job and by combining both styles you can benefit.
To understand both paradigms and how they work in parallel, look at the way your mind works. For example firstly it's procedural; it’s functionally looking around the room thinking of what it's going to do next. This is procedural, it's not working with any objects specifically but it's analysing data which may or may not include objects. Now you've gone through the procedures of looking around the room and decided you want to watch the television.
Now we can work with objects so we shift from the procedural paradigm to the OOP paradigm. Now our mind is in the OOP paradigm for our television object; so we can work with this object easily. Then when we’ve turned the television on, we need to go back to procedural again by making a choice of what program to watch. So now we switch back into procedural mode to think logically about what we want to watch; we're in effect analysing channel data to find what we’re looking for.
You can see by mapping out our minds in the real world we can understand multi paradigm programming with procedural and OOP by observing the shift that occurs. This'll help when building large scale applications that require the ability to implore both of these paradigms to build apps extremely quickly.
When considering analysis could take hours, days, months or even longer it shows procedural is supposed to be harder. It’s slower and can be more difficult depending on the task. However when the analysis is finished we can now decide what object to work with. Our world consists purely of objects so whenever we do something in the real world we’re in the OOP paradigm; wether it’s a television, cooker, lawn mower or any other object type.
Consider also the OOP paradigm is simpler when working with object types. For example we can work with the television type object. It maybe your television or you're friends, however because we have general understanding this television type object, identifying its purpose, we can easily work with that object type. Yes they can differ and they're unique; but regardless the type of object has familiarity with us naturally so it's supposed to be easier in this paradigm when working with objects but not analysis which is procedural and is more difficult sometimes.
Programming 101 course:
youtube.com/playlist?list=PLGC-hHIh7l5s6Spz86OT1u0A7kvQH-2B0
This tutorial is brought to you by avelx.co.uk - Coding tutorials to help you grow.
