Step One: Watch Writing Testable JavaScript - Rebecca Murphey from Full Frontal 2012 (award for worst conference name ever?)
Step Two: Fork this gist.
Step Three: Respond to this question in your fork: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded). Respond below with your thoughts. Did any of the responsibilities that she lists surprise you? Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?
I'll answer the latter question first - hell no. My CRUD applications take all the data in and so everything on it - in one big method.
I like the first step of untagnling your code without writing massive document ready / event handlers to do everything. I also agree that it comes down to design.