Not commenting on the sandboxing but... Writing very strict coding guidelines and specs enforced at build time is a real time saver. For example we're using a

Not commenting on the sandboxing but... Writing very strict coding guidelines and specs enforced at build time is a real time saver. For example we're using a script which verifies that all of the files/directories we've got control on are only using a subset of ASCII. If you're a programmer working on the server-side, you have complete control on the naming of files. Why is it a godsend to use such anal specs? Because external utilities / scripts, on a variety of OSes, will work flawlessly on your files. Otherwise it's all too common to have quoting / escaping issues with this or that script / tool / utility not correctly dealing with space on this or that platform. When you're forced to let the client pick filenames, things gets a bit trickier. But I still do advice very strict naming conventions for all the files that you have control upon. Anyone not admitting that a space in a filename can be problematic hasn't been in this business long enough. (Hint: the problem is not what you have control upon, but what you don't have control upon... And that very article is precisely* proving my point).