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: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded).
-
Did any of the responsibilities that she lists surprise you?
None of the responsibilities surprised me, though I wasn't thinking of client side code in this way before.
-
Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?
I split each feature up similarly to this (starting with the presentation, and then moving to server communication via setup), but I did not think of the entire application in this way.
Step Four: Totally Optional: take a look at some of the other forks and comment if the spirit moves you.
👍