kevin moore kevmo

Generate ssl certificates with Subject Alt Names on OSX

Open ssl.conf in a text editor.

Edit the domain(s) listed under the [alt_names] section so that they match the local domain name you want to use for your project, e.g.

DNS.1   = my-project.dev

Additional FQDNs can be added if required:

#Setting up Nginx on Your Local System ###by Keith Rosenberg

##Step 1 - Homebrew The first thing to do, if you're on a Mac, is to install homebrew from http://mxcl.github.io/homebrew/

The command to type into terminal to install homebrew is:

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

What I Wish I'd Known About Equity Before Joining A Unicorn

Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.

This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would

Why We Use This Checklist:

Hint Health is an enterprise software company with only a handful of engineers. We handle payments for big health care clients, and we can't afford to "just try whatever". We have to balance speed with getting things right the first time. This checklist has been iterated on many times, and has proved very helpful in doing that.
The goal here is to 1.) Make sure you build things people want. And 2.) Surface problems and implications of the design as fast as possible, by reminding ourselves of important questions that can easily get overlooked.

How To Use:

Use the top area to consolidate the latest thinking on the feature. (on that point, we don't use this for bugs or chores. only features)
Use the checklist at the bottom to make sure you're asking the right questions, and do a kick ass job of defining, designing, and implementing the feature.
As soon as you're like... "we should build X", stop and do the User Requirements Pipeline. This

Magic words:

sudo -su postgres
psql -U postgres

If run with -E flag, it will describe the underlaying queries of the \ commands (cool for learning!).

Most \d commands support additional param of __schema__.name__ and accept wildcards like *.*

\q: Quit/Exit

	# General settings
	Host *
	StrictHostKeyChecking no
	ForwardAgent yes
	Compression yes
	ServerAliveInterval 15
	ServerAliveCountMax 4
	UserKnownHostsFile /dev/null
	User kmoore
	Port 22

	// ==UserScript==
	// @name Twitter Cramming
	// @description Force enable cramming (280 character tweets) on Twitter
	// @author Prof. 9
	// @version 0.1
	// @match https://twitter.com/*
	// @run-at document-idle
	// @namespace prof9.twittercramming
	// ==/UserScript==

	import { Component } from "React";

	export var Enhance = ComposedComponent => class extends Component {
	constructor() {
	this.state = { data: null };
	}
	componentDidMount() {
	this.setState({ data: 'Hello' });
	}
	render() {

	<!DOCTYPE html>
	<html>
	<head>
	<title>Box Shadow</title>

	<style>
	.box {
	height: 150px;
	width: 300px;
	margin: 20px;

	var AWS = require('aws-sdk'),
	fs = require('fs');

	// For dev purposes only
	AWS.config.update({ accessKeyId: '...', secretAccessKey: '...' });

	// Read in the file, convert it to base64, store to S3
	fs.readFile('del.txt', function (err, data) {
	if (err) { throw err; }