As a programmer, I love finding ways to keep my code clean and concise. One of the best ways to do this, many would argue, is to use object oriented programming (OOP). This style of coding allows programmers to group similar tasks into classes and eliminate the need for repetitive code. Repetitive code increases file size, looks messy, and becomes a hassle when I need to edit functions.

However, sometimes using object oriented programming requires more effort than it’s worth. In fact, PHP was initially developed as a procedural language and only later extended to OOP. PHP programmers cannot agree on which style is preferable. For me, the most effective method of programming is simply a matter of opinion, the demands of the project, and experience level.

Project Scope

For large-scale web applications, OOP is extremely useful. If the project is likely to require additional functionality at a later time, OOP is a good practice.

For smaller modules, OOP is not always necessary. In these cases, the more abstract quality of the OOP approach tends to add too many unnecessary functions and files, and possibly even be detrimental to website loading times. In my opinion, procedural code can be advantageous when the project requires highly specific functionality that is not likely to be modified at a later time.

Experience Level

While OOP can be very powerful, it becomes less effective when used incorrectly by novices. Learning to program by the OOP approach is more difficult than learning with procedural code, so beginners usually learn the procedural approach. Once they are comfortable with the procedural style, they begin learning OOP. Nevertheless, many highly experienced programmers revert back to procedural programming, arguing that well-written procedural code can be just as powerful as OOP.

By: Sarah