What are some common design patterns used in software development, and when would you apply them?

During my final year project in college, I worked on a group assignment to build a simple weather application. We decided to use the Observer pattern to manage updates from the weather data source to the user interface. Whenever the weather data changed, the UI components automatically updated to reflect the new information without needing to refresh manually. This approach not only made our application responsive but also demonstrated how the Observer pattern can enhance user experience. It was a great learning opportunity to implement this design pattern in a real-world scenario, and it taught me the importance of decoupling the data layer from the presentation layer.

In my volunteer role at a local non-profit, I helped develop a system for managing donations. We faced a challenge with processing different types of donations—monetary, goods, and services. To streamline this, I proposed using the Factory pattern to create donation objects. By implementing a DonationFactory, we could easily produce the right type of donation based on user input. This not only simplified the codebase but also made it easier for our team to add new donation types in the future without modifying existing code. This experience taught me how design patterns can solve specific problems effectively while keeping the code organized.

In my first job as a junior developer, I worked on a project where we needed to manage a single instance of a configuration manager that handled application settings. I recommended using the Singleton pattern to ensure that this instance was globally accessible throughout the application without creating multiple instances. By applying this pattern, we achieved a clean and efficient way to manage configurations, which improved the overall performance and clarity of the code. This experience reinforced my understanding of design patterns and their practical applications in software development.