Unity Game Optimization - Third Edition

Minimizing ongoing code changes

Making code changes to the application in order to hunt down performance issues is best done carefully, as the changes are easy to forget as time wears on. Adding debug logging statements to our code can be tempting, but remember that it costs us time to introduce these calls, recompile our code, and remove these calls once our analysis is complete. In addition, if we forget to remove them, then they can incur unnecessary runtime overhead in the final build since Unity's debug Console window logging can be prohibitively expensive in terms of both CPU and memory.

A good way to combat this problem is to add a flag or comment anywhere we made a change with our name so that it's easy to find and remove it later. ...