Polling can be a good option in many situations, especially when we think about how easy it is to use and what tasks we need to do. Here are some times when I would choose polling instead of using interrupts:

1. Easy to Use: If the system is small or simple, polling is easy to set up. You don’t have to deal with complicated interrupt rules, which helps prevent mistakes in your code.

2. Regular Timing: When you need to do tasks at the same time every time, polling is a reliable way to check for events. For example, if you want to read data from a sensor regularly, polling works well.

3. Rare Events: For tasks that don’t happen often, like checking a button that isn’t pressed, polling can be better. It uses less processing power since there isn’t much waiting around.

4. Limited Resources: In small systems where there aren’t many resources available, polling can help. It avoids the extra work of managing interrupts, which can lead to problems with timing.

In conclusion, choosing between polling and interrupts really depends on what your application needs and how your system is designed.