That&#x27;s a great way to do it: fix-as-you-go. The same goes for adding unit tests where those are missing (in bulk, rather than as a set going with a recently touched piece of code), fixing up documentation issues and other global changes such as naming conventions and so on.<p>Hitting all of the code base in one go with a thing like that is asking for trouble.<p>Downvoters are cordially invited to state why they disagree with this.