Some Background I've been programming for a very long time now. Started on the TI-99/4a near the beginning of 1983 and switched to the C64 in late 1984 / early 1985. Went on to the Amiga, an IBM PC clone in DOS and then Windows. During this time I used a lot of different programming languages and yes nearly everything I was programming was games and game dev tools. When I first moved to Unity I didn't care much for it. I was used to game programming being lean, mean and straightforward (you either programmed in something like Assembler and handled all of the graphics, sound and music support yourself, used C/C++ and chose one of the available libraries (or you could roll your own of course) or used something like AMOS or Blitz. I spent the first week or two researching trying to figure out how to open up Visual Studio and start developing with the Unity API. I knew it had an editor but I thought I could just link to the API as usual and it never occurred to me that I had to use the Editor and begin every project there. Because I never had to do that ever before in my life. Anyway, just to fast forward here... I've spent a lot of time coming to grips with development in Unity and during this time moved from working heavily inside the Editor & using the built-in animation systems, component-based design and so forth for my very first Unity game dev experiment to my current development style. I now use the Editor only to start each project, get the basics set up and use the scene editor itself as an object pooling system. I don't use component-based design any more and I do the bulk of my work outside of the Unity Editor (just programming everything inside Visual Studio). I program games basically the same as I used to before moving to Unity. What's The Point? Several people have contacted me asking for more information about the way I am developing in Unity. These folks all have the same kind of background having previously programmed games in Assembly, C, C# & XNA, etc. And I have seen comments a number of times on the forums where a person says they come from a similar background and are having a lot of difficulty changing over to the Unity Way. It's just such a massive change. So, I wanted to address this by explaining how I develop in Unity and actually build a game that I will provide the source to so you can download, check it out and experiment. It's my hope this will help the folks who have contacted me and also help others coming from a low level game programming background to make Unity work for them.