How does object-oriented programming differ from procedural programming?

During my final year in college, I worked on a project where we developed a library management system. We decided to use object-oriented programming to structure our code. We created classes for books, members, and transactions. This allowed us to encapsulate data and methods related to each class, making the code easier to manage. For instance, when implementing the borrowing process, we had a method in the 'Member' class that checked if a book was available and updated the records accordingly. This modular approach helped us collaborate effectively within our team, as each member could work on different classes without interfering with others' code. The project not only deepened my understanding of OOP concepts but also demonstrated how they can lead to cleaner and more organized code.

While volunteering for a community service organization, I helped organize events that required a structured approach. We used a procedural method to outline the steps for setting up an event—from planning to execution. Each step was a function that we called in sequence, like booking a venue, arranging for food, and inviting attendees. This experience taught me the value of procedural programming in situations where tasks follow a clear linear flow. Although it was less flexible than OOP, it was effective for our needs, showing me how different programming styles can apply to real-world scenarios depending on the project requirements and workflow.

In my first job as a junior developer, I was tasked with creating a simple application for tracking customer feedback. We chose to implement it using OOP principles. By defining classes for customers and feedback, we could easily manage the relationships and interactions between them. This structure allowed us to add new features later, like generating reports, without overhauling the entire system. My experience taught me that while procedural programming might be suitable for smaller tasks, OOP provided the scalability we needed as the project evolved. This understanding of when to apply each paradigm has been invaluable in my early career.