There are common pitfalls in mid-large scale projects. Seasoned developers know to avoid them, how to avoid them, and why to avoid them. Beginners may (or may not) be aware of them, know the solution, and be oblivious to the fact they've missed the point entirely. Before they know what hit them: The project that they put their heart and soul into is a tangled web of interdependent objects and scripts which works great (unless they try to add a new feature or make a trivial change an existing one.) I want to compile advice for ambitious young'uns with big dreams: A big list of what to do (and what not to do) if plan for your next project with a "large scope" to survive it's own development cycle. If there's something that needs done a certain way... It's important for one to understand why so that one can apply the solution correctly when/where it makes sense. You're encouraged to share examples of shortcuts, bad practices, and **** that you might have gotten away with in your first game(s) but will end your first "big" project before you even start it (bonus points if you can "show them the ghost of dev-mas future." What will go wrong if someone continues to do it the wrong way?