Skip to content

Instantly share code, notes, and snippets.

@SteveOscar

SteveOscar/testable-js.markdown

Forked from rrgayhart/testable-js.markdown
Last active April 3, 2016 22:15
Show Gist options
  • Save SteveOscar/e2a9951a24c8dc9b95e681b60135839b to your computer and use it in GitHub Desktop.
Save SteveOscar/e2a9951a24c8dc9b95e681b60135839b to your computer and use it in GitHub Desktop.
Download ZIP
Writing Testable JavaScript
Raw
testable-js.markdown

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 them really surprised me, as they all seem necessary for client-side code, but I found it helpful to have these ideas explicitly stated.

Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?

I definitely didn't consciously break apart responsibilities in my mind, but I think it will help in the future to keep a clearer mental picture of what's happening in my programs. It seems like in JavaScript it's a lot easier to get lost in your own code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment