Can you explain the difference between object-oriented programming and procedural programming?

In my final year of college, I worked on a group project to develop a management system for student clubs. We chose an object-oriented approach because it allowed us to create classes for different entities like 'Student', 'Club', and 'Event'. Each class encapsulated its attributes and methods, making our code organized and easier to maintain. For instance, we had a 'Student' class that could register for events, and this encapsulation enabled us to easily update features without affecting other parts of the system. This experience taught me the importance of OOP in creating scalable applications.

While volunteering for a local charity, I helped organize events using a procedural programming approach with a simple script to automate our registration process. We created step-by-step procedures that collected participant information and sent confirmation emails. This approach was straightforward and efficient for our small-scale needs. However, as the charity grew, we found it challenging to manage changes in the process without breaking the flow. This experience illustrated how procedural programming can be effective for simple tasks but can become cumbersome as complexity increases.

In my first job as a junior developer, I worked on an inventory management system. The team used an object-oriented programming approach, which allowed us to define classes for different inventory items. This made it easy to add new item types without rewriting existing code. I remember creating a 'Product' class that included properties like 'name' and 'quantity' and methods for updating stock levels. This experience showed me how OOP can enhance collaboration among team members, as each developer could work on their class without disrupting the overall system.