JavaScript Blueprints: Client-side architecture patterns

Front-end developers love their JavaScript. It is sleek, powerful and very cool. But how do you architect a strategy for dealing with the (tens of) thousands of lines of code your developers will eventually write not to mention the countless JavaScript libraries your developers want to add to your projects? How do you divvy up the code and organize things in a logical way so that you can find specific code easily? What about namespacing concerns? File management and dynamic loading? Writing libraries for use on both client and server? What tools are available to help you address some of these concerns?

Join us as we explore these and other JavaScript client-side architecture dilemmas.