I hereby claim:
- I am kdawgwilk on github.
- I am kdawgwilk (https://keybase.io/kdawgwilk) on keybase.
- I have a public key ASBEBCeTI6ENqeDBvSJys24fXLiJCBV5e3UQrALUwZjC8wo
To claim this, I am signing this object:
import { createServer } from 'node:http' | |
import { createSchema, createYoga, Repeater } from 'graphql-yoga' | |
import { useDeferStream } from '@graphql-yoga/plugin-defer-stream' | |
import OpenAI from 'openai' | |
const openai = new OpenAI({ | |
// apiKey: 'my api key', // defaults to process.env["OPENAI_API_KEY"] | |
}) | |
const generateCompletion = (prompt: string): Repeater<string> => { |
// Available variables: | |
// - Machine | |
// - interpret | |
// - assign | |
// - send | |
// - sendParent | |
// - spawn | |
// - raise | |
// - actions |
I hereby claim:
To claim this, I am signing this object:
I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.
source 'https://github.com/CocoaPods/Specs.git' | |
use_frameworks! | |
def shared_pods | |
pod 'Fabric' | |
pod 'Crashlytics' | |
end | |
def shared_testing_pods |
# Downloads all the sample txts to the directory where this script is ran | |
import urllib | |
files = ["InsertNames.txt", "DeleteNames.txt", "RetrieveNames.txt", "InsertNamesMedium.txt", "DeleteNamesMedium.txt", | |
"RetrieveNamesMedium.txt", "InsertNamesBig.txt", "DeleteNamesBig.txt", "RetrieveNamesBig.txt"] | |
for filename in files: | |
url = "http://cit.cs.dixie.edu/cs/2420/ssn/%s" % filename | |
file_from_url = urllib.URLopener() | |
file_from_url.retrieve(url, filename) |
Custom recipe to get OS X 10.10 Yosemite running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install.
The software selected is software that is "tried and true" --- software I need after any fresh install. I often install other software not listed here, but is handled in a case-by-case basis.