tmcw

import requests, os, glob, json, sys, webbrowser

you = 'self'
data = 'checkins'

try: os.mkdir(data)
except Exception: pass

cid = 'YOUR_CLIENT_ID'

tmcw

import glob, json

# this script loves this script
# https://gist.github.com/3350235

points = []
vids = set()
places = glob.glob("checkins/*.json")

for p in places:

mojodna

sudo yum -y update
sudo yum-config-manager --enable epel
sudo yum -y install make automake gcc gcc-c++ libcurl-devel proj-devel geos-devel
cd /tmp
curl -L http://download.osgeo.org/gdal/2.0.0/gdal-2.0.0.tar.gz | tar zxf -
cd gdal-2.0.0/
./configure --prefix=/usr/local --without-python
make -j4
sudo make install

marick

Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.

By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.

levity

#!/usr/bin/ruby
LOGIN, PASSWORD = 'your_number', 'your_password'

require 'rubygems'
require 'mechanize'

agent = Mechanize.new

agent.get 'https://wireless.att.com'
login = agent.page.forms_with(:name=>'loginActionForm').first

sgillies

# Swapping x, y coords.

from descartes import PolygonPatch
from fiona import collection
from itertools import imap
import logging
from matplotlib import pyplot

log = logging.getLogger()

mourner

// Lefalet shortcuts for common tile providers - is it worth adding such 1.5kb to Leaflet core?

L.TileLayer.Common = L.TileLayer.extend({
	initialize: function (options) {
		L.TileLayer.prototype.initialize.call(this, this.url, options);
	}
});

(function () {
	

Calzzetta

import cx_Oracle

def perform_query(query, bind_variables):
    connection = db_pool.acquire()
    cursor = connection.cursor()
    cursor.execute(query, bind_variables)
    result = cursor.fetchall()
    cursor.close()
    db_pool.release(connection)
    return result

whyvez

#!/bin/bash
#
# Script to setup a Elastic Beanstalk AMI with geospatial libraries and postGIS
#
# sh aws_ami_prep.sh > aws_ami_prep.log 2>&1 &

# Go to ec2-user home directory
cd /home/ec2-user

# yum libraries

twolfson

We prefer to have audit logging in our services that leverage databases. It gives us clarity into sources of where ACL issues might originate as well as gives us a general timeline of activity in our application.

Audit logging is tedious to set up so this gist contains our latest iteration of audit logging support for a sequelize based service.