Skip to content

Instantly share code, notes, and snippets.

@bethsecor

bethsecor/testable-js.markdown Secret

Forked from rrgayhart/testable-js.markdown
Last active April 3, 2016 01:27
Show Gist options
  • Save bethsecor/f90087c8ba0b4c4c79e89bdac65aae43 to your computer and use it in GitHub Desktop.
Save bethsecor/f90087c8ba0b4c4c79e89bdac65aae43 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?

    The four responsibilities are presentation and interaction, data/server communication, application state, and setup. None of these really surprised me, and it was nice to see these broken down this way and refactored.

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

    I would say I probably never thought of the application state as a separate piece, but that makes a lot more sense now. I don't think I ever thought of setup either. I definitely thought of presentation and data as separate things.

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