One of the issues that you can run into when developing with Unity is that logging is quite expensive. It's entirely possible, if you're trying to log a verbose amount of processing for one reason or another, you can end up crippling the framerate of your game. There are performance

Or: why micro-optimising games code often helps. I was part of a conversation on Twitter that started with a question about the relative performance of calling .GetComponent<T>() vs having a public field assigned in the inspector. I linked back to my earlier post that includes a profiling

As part of my ongoing involvement with Big Robot I've been doing a bit of work recently on working out "how best to do things" in Unity3d. Some of the output of that might turn up in a later post, but, since this is my first post in