Uploaded April 2017 | Updated September 2026, 2 weeks ago

---

I’ve recently done lectures about programming and paradigms or models about programming styles. There are two main types OOP and procedural but most programmers ignore modular programming discontinuing it as a brand of OOP programming.

However this couldn’t be further from the truth! Procedural programming has a modular side called modular programming. This is where we take a flat file of subroutines or functions and variables and place them within an object scope. When placing variables (properties) and functions (methods) into an object we can have private members and a nice way to organise our application logic.
These modules in our program are objects however that doesn’t mean to say we are using OOP. It’s all about what we’re constructing the object for. Are we constructing an object we’re pulling out of the database? If so it’s object oriented programming.

But are we constructing an object for a library or module? If yes this is part of the application logic and is modular programming not object oriented programming. This means we construct this object not for an object store or data we fetch from a database; but instead for modularity for application logic.