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

During my time in college, I took an introductory programming course where we learned about procedural and object-oriented programming. In one of our projects, we had to create a simple banking system. I implemented it using procedural programming, focusing on functions to handle transactions like deposits and withdrawals. This approach was straightforward, but as the project grew, I realized it became harder to manage. I later had the opportunity to refactor my code using OOP concepts, creating classes for accounts and transactions. This allowed me to encapsulate data and methods, making the code more organized and easier to understand. It was a valuable lesson in how different programming styles can impact the maintainability of a project.

While volunteering for a local non-profit, I was part of a team tasked with creating a website to promote our events. I initially used procedural programming to build a simple page that showcased our event details. However, as we needed to add more features, like a registration form and event calendars, I suggested we switch to an object-oriented approach. This allowed us to create reusable components, such as user profiles and event objects, which made it easier to manage and expand the website. By using OOP, we improved the website’s structure, making it more efficient and easier for future volunteers to add content.

In my first job as a junior developer, I worked on a team that was developing an inventory management system. Initially, we used procedural programming for some of the basic features, which worked fine for smaller tasks. However, as the system expanded, I proposed that we use OOP principles to develop new features, such as a product catalog and order processing. By creating classes and objects, we were able to streamline workflows and enhance the system's scalability. This experience reinforced my understanding of how both procedural and object-oriented concepts can coexist, providing flexibility depending on the project's needs.