| var faker = require('faker') | |
| var fs = require('fs') | |
| var path = require('path') | |
| for (var i = 0; i < 1000; i++) { | |
| generateMD() | |
| } | |
| function generateMD () { | |
| var fileName = faker.lorem.word() + '-' + faker.lorem.word() |
| // A script that can pull down the result of the introspection query | |
| // from a running graphql server. | |
| // Dependencies: | |
| // npm i -S isomorphic-fetch graphql-tag graphql apollo-client | |
| // Usage: | |
| // node fetch-graphql-schema [graphql url] | |
| // Example: |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
You probably arrived here because of a curt message in response to an issue you filed on a repo that I contribute to. Sorry about that (particularly if you filed the issue long ago and have been waiting patiently for a response). Let me explain:
I work on a lot of different open source projects. I really do like building software that makes other people's lives easier, but it's crazy time-consuming. One of the most time-consuming parts is responding to issues. A lot of OSS maintainers will bend over backwards to try and understand your specific problem and diagnose it, to the point of setting up new test projects, fussing around with different Node versions, reading the documentation for build tools that we don't use, debugging problems in third party dependencies that appear to be involved in the problem... and so on. I've personally spent hundreds of hours of my free time doing these sorts of things to try and help people out, because I want to be a responsible maintainer and I
| body { | |
| color: #212121; | |
| font-family: "Helvetica Neue", "Calibri Light", Roboto, sans-serif; | |
| -webkit-font-smoothing: antialiased; | |
| -moz-osx-font-smoothing: grayscale; | |
| letter-spacing: 0.02em; | |
| } |
Kinesis Freestyle (Terrible key switches. Mushy and un-lovable)
Kinesis Freestyle Edge (Traditional layout with too many keys, mech switches, proably too big to be tented easily/properly)
Matias Ergo Pro (Looks pretty great. Have not tried.)
ErgoDox Kit (Currently, my everyday keyboard. Can buy pre-assembled on eBay.)
ErgoDox EZ (Prolly the best option for most people.)
| exports.handler = function(event, context) { | |
| // We'd get this from the Lambda event in reality | |
| var sampleInput = { | |
| from: 1, | |
| to: 39, | |
| bucketName: 'test-bucket', | |
| imageSizes: [{ | |
| width: 600, | |
| height: 400, | |
| description: 'A medium thumbnail', |
| Originall From: Posted 2015-05-29 http://ubwg.net/b/full-list-of-ffmpeg-flags-and-options | |
| This is the complete list that’s outputted by ffmpeg when running ffmpeg -h full. | |
| usage: ffmpeg [options] [[infile options] -i infile]… {[outfile options] outfile}… | |
| Getting help: | |
| -h — print basic options | |
| -h long — print more options | |
| -h full — print all options (including all format and codec specific options, very long) |
| function _confidence(ups, downs) { | |
| var n = ups + downs; | |
| if(n === 0) { | |
| return 0; | |
| } | |
| var z = 1.281551565545; | |
| var p = parseFloat(ups) / n; | |
| var left = p + 1 / (2 * n) * z * z; |
| /* | |
| * Verify GitHub webhook signature header in Node.js | |
| * Written by stigok and others (see gist link for contributor comments) | |
| * https://gist.github.com/stigok/57d075c1cf2a609cb758898c0b202428 | |
| * Licensed CC0 1.0 Universal | |
| */ | |
| const crypto = require('crypto') | |
| const express = require('express') | |
| const bodyParser = require('body-parser') |