anchor.diff:  
   In the spring of 2014 I decided I needed a change and decided I wanted to become a JavaScript full stack programmer.  I started attending [UtahJS] meetups in the Salt Lake City area.  Early that summer there was a UtahJS Conference.  While attending I met another novice JS developer.  We were both really happy to see each other at the next UtahJS meetup.  After that meetup, we were talking about how hard it was to learn code in isolation, and thus was born the SLC JS Learners' group.
   
  -Since that fateful day, the SLC JS Learners' group has grown to more than 600 members, so big we're actually merging into the UtahJS group, and I've gotten a lot of novices up and running!  The following resources are the things I most frequently share with my fellow learners.
  +Since that fateful day, the SLC JS Learners' group has grown to more than 600 members, so big we're actually merging into the UtahJS group, and I've gotten a lot of novices up and running!  The following resources are the things I most frequently share with my fellow learners.  
   
   
   ## JavaScript
  
positive.code: 
  Once you start actually coding in JavaScript, you will likely start to wonder what is happening under the hood.  To get a glimpse, I recommend running your code through the http://pythontutor.com/javascript.html#mode=edit[JavaScript version of the PythonTutor].   
  
  ### Dive Deep
  
  Once you've gotten through the "Basic JavaScript" exercise, I recommend you start to learn more about how JavaScript works "under the hood".
  
negative.code: Test-Driven Development is a wonderful thing, but as a novice it can be overwhelming.  I encourage Learners' to start practicing TDD when they start working through http://codekata.com/[CodeKata].  It has it's own flavor of TDD, but the principals will carry over to other TDD libraries.  Writing your own tests for CodeKatas helps you work through the principals of TDD.
  
  
  
  ### GitHub vs GitLab
  
  