A while ago I sat down and fixed all the warnings coming out of a C embedded project. It was a real eye opener and not only did the code get more readable it also helped me clean up a few edge case errors I had missed.
I have been programming professionally for over thirty years and most mentors used to shrug at warnings if the code worked.
It inspired me to go back and clean up my C# and Java stuff and as a learning process I highly recommend it. It seems especially valuable in fast changing environments, generally you will upgrade a tool and get new warnings. I used to think they were just a pain but now I treat them like a way of gaining new insights.
I have been programming professionally for over thirty years and most mentors used to shrug at warnings if the code worked.
It inspired me to go back and clean up my C# and Java stuff and as a learning process I highly recommend it. It seems especially valuable in fast changing environments, generally you will upgrade a tool and get new warnings. I used to think they were just a pain but now I treat them like a way of gaining new insights.