minrwhite

#!/usr/bin/env bash
set -e

declare -A first_start

function handle_event() {
    local entry="$1"
    local action=$(echo $entry | jq -r '.action')
    local service=$(echo $entry | jq -r '.service')
    local hook="./hooks/$service/$action"

minrwhite

FROM httpd:2.4-alpine

COPY server.crt server.key /usr/local/apache2/conf/
RUN sed -e "s/^#Include conf\/extra\/httpd-ssl.conf$/Include conf\/extra\/httpd-ssl.conf/g;s/^#LoadModule ssl_module modules\/mod_ssl.so$/LoadModule ssl_module modules\/mod_ssl.so/g;s/^#LoadModule socache_shmcb_module modules\/mod_socache_shmcb.so$/LoadModule socache_shmcb_module modules\/mod_socache_shmcb.so/g" -i /usr/local/apache2/conf/httpd.conf

minrwhite

{
  "address": "<public ip address>",
  "ca": "<ca-cert-path>",
  "ca-key": "<ca-key-path>",
  "tls-cert": "<tls-cert-path>",
  "tls-key": "<tls-key-path>",
  "responder": "<oscp-cert-path>",
  "responder-key": "<oscp-key-path>",
  "db-config": "/cfssl-config/db-config.json",
  "signing": {

minrwhite

*.pem
*.csr

minrwhite

var http2 = require('http2'),
    fs = require('fs'),
    url = require('url'),
    options = {
        key: fs.readFileSync('./ssl/server.key'),
        cert: fs.readFileSync('./ssl/server.cert')
    };

http2.createServer(options, function(request, response) {
    if (url.parse(request.url).pathname === '/mystyles.css') {

minrwhite

Keybase proof

I hereby claim:

• I am benwhite-deltas on github.
• I am benwhitedeltas (https://keybase.io/benwhitedeltas) on keybase.
• I have a public key whose fingerprint is 0677 6249 0FEC F39E 64DB 02B1 DE3E 1A3B 329A 0A99

To claim this, I am signing this object:

minrwhite

minrwhite

Git DMZ Flow

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.

• Two developers working on independent features must never be blocked by each other
  • No code freeze! Ever! For any reason!
• A developer must be able to base derivative work on another developer's work, without waiting for any third party
• Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
• Developers must be able to work on multiple features simultaneously, or at lea

minrwhite

set logscale x
set logscale y
plot "plot.csv" using 1:2 with lines, "plot.csv" using 1:3  with lines
pause -1

minrwhite

Catch common usability problems before user testing with this checklist. I can add suggestions on https://userium.com/ 

USER EXPERIENCE

Personalized features. Currency, language, country specific deals, taxes, or delivery options are changed based on user's location. IP-based geolocation is not enabled without user's permission.

Registering provides value to users. For example a "Free Trial" button communicates a clear benefit, but a "Register" button doesn't. Unnecessary registration is avoided.

Transparent pricing. Prices are clearly displayed. There are no hidden costs or surprises in the terms.