Skip to content

Instantly share code, notes, and snippets.

View geocodinglife's full-sized avatar
👨‍💻
Keep Coding

Ricardo Alarcon geocodinglife

👨‍💻
Keep Coding
  • remote
View GitHub Profile

Moving from jQuery

Events

// jQuery
$(document).ready(function() {
  // code
})
def authentication(string, need = {dog: 1, cocodrilo: 2})
string1 = string.split(" ")
if string1 == dog, string1 == cocodrilo
puts "success"
end
@geocodinglife
geocodinglife / node-folder-structure-options.md
Created August 25, 2017 16:57 — forked from lancejpollard/node-folder-structure-options.md
What is your folder-structure preference for a large-scale Node.js project?

What is your folder-structure preference for a large-scale Node.js project?

0: Starting from Rails

This is the reference point. All the other options are based off this.

|-- app
|   |-- controllers
|   |   |-- admin
@geocodinglife
geocodinglife / syntax.md
Created September 10, 2017 04:22 — forked from wearethefoos/syntax.md
Ruby vs JS vs ES6

Variables

Ruby

Name a value.

color = "red"
@geocodinglife
geocodinglife / README.md
Created October 25, 2017 01:59 — forked from hofmannsven/README.md
My simply Git Cheatsheet
@geocodinglife
geocodinglife / GitHub-Forking.md
Created October 25, 2017 17:00 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

@geocodinglife
geocodinglife / gist:da836aad863b23b38dddabe03de5e64d
Created November 24, 2017 20:55 — forked from rxaviers/gist:7360908
Complete list of github markdown emoji markup

People

:bowtie: :bowtie: 😄 :smile: 😆 :laughing:
😊 :blush: 😃 :smiley: ☺️ :relaxed:
😏 :smirk: 😍 :heart_eyes: 😘 :kissing_heart:
😚 :kissing_closed_eyes: 😳 :flushed: 😌 :relieved:
😆 :satisfied: 😁 :grin: 😉 :wink:
😜 :stuck_out_tongue_winking_eye: 😝 :stuck_out_tongue_closed_eyes: 😀 :grinning:
😗 :kissing: 😙 :kissing_smiling_eyes: 😛 :stuck_out_tongue:

What is your folder-structure preference for a large-scale Node.js project?

0: Starting from Rails

This is the reference point. All the other options are based off this.

|-- app
|   |-- controllers
|   |   |-- admin
@geocodinglife
geocodinglife / 42-things.md
Created October 23, 2018 00:14 — forked from xdite/42-things.md
Ten (42) Things You Didn't Know Rails Could Do