Skip to content

Instantly share code, notes, and snippets.

View alvarezmelissa87's full-sized avatar

Melissa Alvarez alvarezmelissa87

View GitHub Profile
@alvarezmelissa87
alvarezmelissa87 / file1.txt
Created January 1, 2016 23:42
Created via API
Demo
WHAT IS IT?
Sidekiq is a framework for performing background processes. It allows you to scale your application by
performing work in the background. Tasks can be set to automatically start being processed
in the background asynchronously. For example, if your app needed to send out emails on a regular basis,
the best way to do that would be to do it as a background task. Sidekiq allows you to do this easily.
SOME GOOD STUFF
Sidekiq is Resque compatiple- it can be integrated into an existing project that uses
@alvarezmelissa87
alvarezmelissa87 / jquery_example.html
Last active August 29, 2015 13:57 — forked from dbc-challenges/jquery_example.html
Intro to jQuery for Phase 0
//Reflection:
// This has been one of the most helpful challenges yet! I learned so much about jQuery. I thought it would've been helpful
// to have had some kind of instructional assignment first but it definitely allowed me to get my hands dirty. It opened my
// eyes to how much you can actually do using jQuery in JavaScript. It helped me see all of the places that I need more
// knowledge in (going to do both codeacademy and codeschool tutorials as well as review the source provided on the objectives
// page). The most challenging part was figuring out how the animation worked and how you have to nest functions withing
// functions for different events. The most beneficial part of this challenge was allowing me to glimpse the amazing
// possibilities that jQuery offers and giving me a framework for how to approach learning it.
@alvarezmelissa87
alvarezmelissa87 / 0.2.1-boggle_class_from_methods.rb
Last active August 29, 2015 13:56 — forked from dbc-challenges/0.2.1-boggle_class_from_methods.rb
phase 0 unit 2 week 1boggle class challenge
# OBJECTIVE 1: Instantiate new BobbleBoard class which will have methods from last challenge (#create_word, #get_row, #get_column)
class BoggleBoard
attr_reader :board # I removed one of the parameters that the methods took before they were part of
# the BoggleBoard class- the board parameter -where you had to pass a nested array as one of the
def initialize(board) # arguments so that the method knew what to do its method to. In this case, you're initializing
@board = board # an instance of the BoggleBoard class with a nested array (dice_grid, in this case) so you don't
end # have to specify a board parameter for each method within the class. You create the instance variable
# that will stand for it and then can just use it in the methods within the class.
def create_word(*coords)