Best practices for handling warnings

Question

The project I'm currently working on generates 30+ warnings each time it gets build. They were ignored from the beginning of the projects. I guess due to the lack of policy about warnings.

How do you usually handle this? Ignore them altogether? Try to fix them all at once (this requires some time)? Or just fix bit by bit along the way?

Answer 1

In our development team, each person needs to clean up their warnings before beer o'clock on Friday. If you do not fix your warnings - no beer for you. It is surprisingly a good motivator.