I've just started working with this new developer with this way of coding that
leaves me constantly confused and I'm wondering if there are any guides as to
how you should structure your code and design in Flash.

This project is a skin for a .NET application that installs onto the client's
machine.

So he has some code for performing calculations and rendering their results is
a graphical manner stored in external class files. Then it appears he has got
tired of not having visual control of the output so he's then made up a string
of different .fla/.swf's that all import with the MovieClipLoader into his
project all on different levels. Now he comes from a C++ background so he's
using UI components like cigarettes at the PhillipMorris AGM and wonders where
all his memory is going (not to say that full screen scaling of bitmap
backgrounds is also fine).

Now I come from the school of build everything so it lives on one frame. Build
all MC's within the one file and then store them in the library until needed .
Also stay away from components with a mighty long pole because they either eat
memory, filesize or don't give you the control you need.

So it's rather clear that there are different ways of building files that goes
far beyond the simple tips scattered through the documentation (even so at
point's it shows completely different techniques in the sample code).

Thus are there any sites (or even books) that cover entire project layout and
different ways at that.

Cheers!