Denis A da115115

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

Deploy your site with git

This gist assumes:

you have a local git repo
with an online remote repository (github / bitbucket etc)
and a cloud server (Rackspace cloud / Amazon EC2 etc)
- your (PHP) scripts are served from /var/www/html/
- your webpages are executed by apache
apache's home directory is /var/www/

Creating a Happy Git Environment on OS X

Step 1: Install Git

brew install git bash-completion

Configure things:

git config --global user.name "Your Name"

git config --global user.email "[email protected]"

Description

PLEASE SCROLL DOWN AND READ THE COMMENTS FOR A MORE UP TO DATE WAY (AND EASIER) TO DO THIS
When using Homebrew (http://brew.sh) and searching formulas or pull requests you may get the dreaded error message: Github API Rate limit exceeded

Let's fix that! (yeah!)

Short version

PLEASE SCROLL DOWN AND READ THE COMMENTS FOR A MORE UP TO DATE WAY (AND EASIER) TO DO THIS

	# If you work with git, you've probably had that nagging sensation of not knowing what branch you are on. Worry no longer!

	export PS1="\\w:\$(git branch 2>/dev/null \| grep '^*' \| colrm 1 2)\$ "

	# This will change your prompt to display not only your working directory but also your current git branch, if you have one. Pretty nifty!

	# ~/code/web:beta_directory$ git checkout master
	# Switched to branch "master"
	# ~/code/web:master$ git checkout beta_directory
	# Switched to branch "beta_directory"

	#!/bin/bash
	#===============================================================================
	#
	# FILE: getgeo.sh
	#
	# USAGE: ./getgeo.sh
	#
	# DESCRIPTION: run the script so that the geodata will be downloaded and inserted into your
	# database
	#

	def flatten_dict(root, prefix_keys=True):
	dicts = [([], root)]
	ret = {}
	seen = set()
	for path, d in dicts:
	if id(d) in seen:
	continue
	seen.add(id(d))
	for k, v in d.items():
	new_path = path + [k]

	import com.amazonaws.auth.BasicAWSCredentials
	import com.amazonaws.services.s3.AmazonS3Client
	import com.amazonaws.AmazonClientException
	import com.amazonaws.AmazonServiceException
	import java.io.File
	import java.io.BufferedReader
	import java.io.InputStreamReader
	import java.io.FileOutputStream
	import org.apache.commons.io.IOUtils

	#!/usr/bin/env bash

	# list_hadoop_codecs.sh
	#
	# USAGE:
	# curl -sL https://gist.github.com/chetan/6524829/raw/list_hadoop_codecs.sh \| bash

	# make sure hadoop is avail
	if [[ -z `which hadoop 2>/dev/null` ]]; then
	echo "hadoop command not found!"

	"""
	example: The following JSON document:
	{"maps":[{"id1":"blabla","iscategorical1":"0", "perro":[{"dog1": "1", "dog2": "2"}]},{"id2":"blabla","iscategorical2":"0"}],
	"masks":{"id":"valore"},
	"om_points":"value",
	"parameters":{"id":"valore"}}

	will have the following output:
	{'masks.id': 'valore', 'maps.iscategorical2': '0', 'om_points': 'value', 'maps.iscategorical1': '0',
	'maps.id1': 'blabla', 'parameters.id': 'valore', 'maps.perro.dog2': '2', 'maps.perro.dog1': '1', 'maps.id2': 'blabla'}