It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.
{ | |
"emojis": [ | |
{"emoji": "👩👩👧👧", "name": "family: woman, woman, girl, girl", "shortname": ":woman_woman_girl_girl:", "unicode": "1F469 200D 1F469 200D 1F467 200D 1F467", "html": "👩‍👩‍👧‍👧", "category": "People & Body (family)", "order": ""}, | |
{"emoji": "👩👩👧👦", "name": "family: woman, woman, girl, boy", "shortname": ":woman_woman_girl_boy:", "unicode": "1F469 200D 1F469 200D 1F467 200D 1F466", "html": "👩‍👩‍👧‍👦", "category": "People & Body (family)", "order": ""}, | |
{"emoji": "👩👩👦👦", "name": "family: woman, woman, boy, boy", "shortname": ":woman_woman_boy_boy:", "unicode": "1F469 200D 1F469 200D 1F466 200D 1F466", "html": "👩‍👩‍👦‍👦", "category": "People & Body (family)", "order": ""}, | |
{"emoji": "👨👩👧👧", "name": "family: man, woman, girl, girl", "shortname": ":man_woman_girl_girl:", "unicode": "1F468 200D 1F469 200D 1F467 200D 1F467", "html": "👨‍👩&z |
#!/usr/bin/env python | |
""" | |
Converts Internet Explorer 'capture network traffic' XML to a HAR file. | |
Turns out that XML is just a HAR file anyways, but in XML form. So this | |
just converts it to JSON, and Bob's your uncle. | |
Requires Python 2.7+ and LXML. | |
""" | |
from __future__ import unicode_literals |
Just like how we use Git to version control source code, we use migrations to manage the state of our database schemas.
Imagine you're working on project with another developer, and you're both tasked with creating a specific part of an event planning application. Let's say you are in charge of creating the Users
and your friend is going to create the Events
.
Let's say you and your friend divided the work in a way so that neither of you will have to to use each other's code to finish your tasks. While you're working on your part of the application, you only really need to touch the Users
table when you are working with the database.
Just like how we use Git to version control source code, we use migrations to manage the state of our database schemas.
Imagine you're working on project with another developer, and you're both tasked with creating a specific part of an event planning application. Let's say you are in charge of creating the Users
and your friend is going to create the Events
.
Let's say you and your friend divided the work in a way so that neither of you will have to to use each other's code to finish your tasks. While you're working on your part of the application, you only really need to touch the Users
table when you are working with the database.
Make sure that the project you are in is a node project (it has a package.json
) and you have already installed and initialized sequelize (npm install --save sequelize
, sequelize init
). Also make sure that your config.json
file has the correct credentials to connect to your database.
/* Double all numbers */ | |
Promise.map([1, 2, 3], function(num) { | |
return num * 2; | |
}).then(function(numbers) { | |
console.log("The final list of numbers:", numbers); | |
//The final list of numbers: [ 2, 4, 6 ] | |
}); | |
/* Remove all the odd numbers */ | |
Promise.filter([1, 2, 3], function(num) { |
" A minimal vimrc for new vim users to start with. | |
" | |
" Referenced here: http://vimuniversity.com/samples/your-first-vimrc-should-be-nearly-empty | |
" | |
" Original Author: Bram Moolenaar <[email protected]> | |
" Made more minimal by: Ben Orenstein | |
" Modified by : Ben McCormick | |
" Last change: 2014 June 8 | |
" | |
" To use it, copy it to |
var app = require('express')(); | |
var GridStore = require('mongodb').GridStore; | |
var ObjectID = require('mongodb').ObjectID; | |
var MongoClient = require('mongodb').MongoClient; | |
var Server = require('mongodb').Server; | |
var dbConnection; | |
MongoClient.connect("mongodb://localhost:27017/ersatz?auto_reconnect", {journal: true}, function(err, db) { | |
dbConnection = db; | |
app.listen(3000); |