6 things I wish I knew about Unity3D when I first started.

If you are a traditional game programmer such as myself, and never really dealt much with scripting then learning some of the paradigms of Unity3D can be somewhat shocking. It's easy to learn once you change the way you think about how you are making games. Here are a few things I wish I would have known about Unity3D.

I started looking into Unity a while ago after seeing all the cool stuff people were building with it and hearing about how easy it was to build games with.
My background up to this point had been building games for windows, the traditional build everything yourself way. When the mobile craze hit, I started working on mobile games using Marmalade which was a natural transition for me. Everything worked exactly the same and I was able to port a lot of my tech over without too many issues.
After having built a few mobile games I started looking into Unity3D. It was very different than what I was working with up to this point. What really attracted me to it was that in my mind, I had always envisioned building a tech similar to this for creating games. My dream engine looked a lot like unity, where games could be built by using high level game objects to which components could be attached. I built this concept in my Rebel Tech engine, except instead of running script you would simply attach C++ classes to objects to give them interesting behaviors. Basically Unity3d to me was what I would have taken me 30 years to build by myself.

Lady - Unity3D fan