Skip to content

Instantly share code, notes, and snippets.

View erinnachen's full-sized avatar

Erinna Chen erinnachen

17 followers · 1 following
  • GitHub Staff
  • Seattle, WA
View GitHub Profile
@erinnachen
erinnachen / require-1511.markdown
Created May 24, 2016 13:27 — forked from rrgayhart/require-1511.markdown
The Concept of Require

When you start working with WebPack for GameTime, you'll notice that you can't just define a variable in one file and find it in another as easily as you can in Rails.

Read Node.js, Require and Exports and Organize Your Code with RequireJS

Fork this gist and answer the following questions:

  • In the context of Node, what is a module?
  • The code examples from the second blog post look very different from the first. Why?
@erinnachen
erinnachen / gist:dd8632a2130f5762dc975867c62aa6c4
Created May 20, 2016 14:05 — forked from stevekinney/gist:9e9cfeb225c8133fda73
**Step One**: Watch [Sorting Algorithms in JavaScript](https://www.youtube.com/watch?v=uRyqlhjXYQI)
**Step Two**: Fork this gist.
**Step Three**: Respond to this question in your fork: "What are some of the balances and trade offs between different sorting algoritms?"
**Step Four**: _Totally Optional_: take a look at some of the other forks and comment if the spirit moves you.
@erinnachen
erinnachen / git-workflow.markdown
Last active December 18, 2018 16:48
My Git Workflow

Project workflow:

  1. Load/Reload waffle.
  2. Choose a card from the backlog in waffle. If we're working separately, it's best to move that card that you've chosen into ready and perhaps assign it to yourself as well.
  3. git checkout master
  4. git pull origin master
  5. run rspec
  6. Checkout a new branch and tag it with #issue_number
  7. Write the feature test associated with your waffle card.
  8. Run rspec, and make sure that there are no errors that blow up the stack (missing ends, forgetting capitalization, etc.)
  9. commit your feature test
@erinnachen
erinnachen / cfu_crud_in_sinatra.markdown
Last active February 2, 2016 23:05 — forked from rwarbelow/cfu_crud_in_sinatra.markdown
CRUD in Sinatra -- Check for Understanding

  1. Define CRUD. CRUD stands for C reate, R ead/Retrieve, U pdate, D elete and these refer to the four functions for working with stored information.

  2. There are seven verb + path combinations that are necessary in a basic Sinatra app in order to provide full CRUD functionality. List each of the seven combinations, and explain what each is for.

  • Verb: GET Path: /index See all the items that are stored (Read)
  • Verb: GET Path: /item See a single item that is stored (Read)
  • Verb: GET Path: /new Load a form in order to create a new item in the database (Create)
  • Verb: POST Path: /index Store the item in the database (Create)
  • Verb: GET Path: /item/update Load a form in order to update the attributes of an item (Update)