Skip to content

Instantly share code, notes, and snippets.

View ksk5280's full-sized avatar

Kimiko Kano ksk5280

17 followers · 18 following
View GitHub Profile
@ksk5280
ksk5280 / require-1511.markdown
Last active May 17, 2016 04:59 — 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?
  • It's the fundamental Node building block, which is related to a single file. Anything within the module is private.
@ksk5280
ksk5280 / gist:63debf5b3989a324da871b4112700a76
Last active May 14, 2016 23:10 — forked from stevekinney/gist:9e9cfeb225c8133fda73
Sorting Algorithms
**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?"
Bubble sort is very slow. It's mostly used for instructional purposes to show as a comparison to the other sorting methods.
Insertion sort is simple and doesn't require using a lot of space, so it can be a good algorithm to use if there's a limit in how much memory you have. It's relatively fast for a small amount of data.
Merge sort is fast but requires more memory than insertion sort, which you might not have.
@ksk5280
ksk5280 / gist:7ae8ae5f81449b5028f12f32b33d1b66
Created April 22, 2016 22:03 — forked from thePaulista/gist:89cd10d2ad2d3b53bbfdb94bfb4576cb
Vim Tips and Resource
Cheat Sheet:
http://vim.rtorr.com/ (START with this one)
http://www.catswhocode.com/blog/130-essential-vim-commands
Vim Adventure: vim game to help you with navigation.
http://vim-adventures.com/
Vim Golf: check your keystroke count. It's the exercism of vim.
http://www.vimgolf.com/
@ksk5280
ksk5280 / git-workflow.markdown
Created March 11, 2016 17:11 — forked from erinnachen/git-workflow.markdown
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
@ksk5280
ksk5280 / setting_expectations.markdown
Created February 29, 2016 21:06 — forked from rwarbelow/setting_expectations.markdown
Setting Expectations

Setting Group Expectations

Group Member Names:

  1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?

@ksk5280
ksk5280 / cfu_crud_in_sinatra.markdown
Last active February 3, 2016 20:15 — forked from rwarbelow/cfu_crud_in_sinatra.markdown
CRUD in Sinatra -- Check for Understanding
  1. Define CRUD. Four main functions a user can use to manipulate data: Create, Read, Update, Delete
  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. Using the Task Manager example:
    1. "/tasks", GET: shows all tasks
    2. "/tasks/:id", GET: shows one task
    3. "/tasks/new", GET: shows form to create a new task
    4. "/tasks", POST: creates a new task
    5. "/tasks/:id/edit", GET: shows form to edit a task
  1. "/tasks/:id", PUT: submit form to update existing task