DRYing out your client-side apps

There's plenty of cool stuff Node offers purely in terms of server-side architectures, but it also offers a way to solve a problem we've been wrestling with since client-side applications became a big deal: writing everything twice. Rather than having the templates that produce markup exist in one backend language and in JavaScript, you can reuse them. Instead of validating in JavaScript on the client for the user's convenience and then again in some other language on the server for security, you can share a validation module that can be used in both scenarios. And so on. We'll look at some of the ways to stop repeating ourselves in Node apps and focus on getting the most out of existing client-side code.

Speaker Bio

I'm a JavaScript developer living in Austin, TX with my dog and cat. My interest in Node stems from a history as a backend developer combined with a love of client-side apps. I sometimes maintain a colorful blog, I've spoken at a handful of JavaScript conferences, and I'm the author of "Node for Front-End Developers" from O'Reilly. When I get up from the computer, I'm remodeling my house.

Links

Blog: http://garann.com/dev
Github: http://github.com/garann