blisabda

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

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

Install Vagrant

sudo su
apt-get update && apt-get install -y libvirt-dev ruby-all-dev apparmor-utils
curl -O -L https://dl.bintray.com/mitchellh/vagrant/vagrant_1.6.5_x86_64.deb
dpkg -i vagrant_1.6.5_x86_64.deb 
aa-complain /usr/lib/libvirt/virt-aa-helper # workaround
exit

Install vagrant-kvm as user

Linux NetFilter, IP Tables and Conntrack Diagrams

IPTABLES TABLES and CHAINS

IPTables has the following 4 built-in tables.

1) Filter Table

Filter is default table for iptables. So, if you don’t define you own table, you’ll be using filter table. Iptables’s filter table has the following built-in chains.

	##############################################################################
	# History Configuration
	##############################################################################
	HISTSIZE=5000 #How many lines of history to keep in memory
	HISTFILE=~/.zsh_history #Where to save history to disk
	SAVEHIST=5000 #Number of history entries to save to disk
	#HISTDUP=erase #Erase duplicates in the history file
	setopt appendhistory #Append history to the history file (no overwriting)
	setopt sharehistory #Share history across terminals
	setopt incappendhistory #Immediately append to the history file, not just when a term is killed

	#!/bin/bash

	#### This script is published by Philipp Klaus <[email protected]>
	#### on <http://blog.philippklaus.de/2011/05/ipv6-6in4-tunnel-via-hurricane-electric-tunnelbroker-net-automatic-ip-update-on-mac-os-x/>
	#### It is originally by freese60 and modified by limemonkey.
	#### Found on <http://www.tunnelbroker.net/forums/index.php?topic=287.0>

	### Uncomment this line to debug the script:
	#set -x

	machine github.com
	login technoweenie
	password SECRET

	machine api.github.com
	login technoweenie
	password SECRET

	#!/usr/bin/env zsh

	git show-branch -a \
	\| grep '\*' \
	\| grep -v `git rev-parse --abbrev-ref HEAD` \
	\| head -n1 \
	\| sed 's/.\[\(.\)\].*/\1/' \
	\| sed 's/[\^~].*//'

	# How it works:

	# Matching 'SSL SERVER HELLO' packets using IPtables
	# Using some connection tracking to make sure not
	# to match randomly in the middle of some huge SSL
	# session.

	iptables --insert INPUT -p tcp --sport 443 \
	-m connbytes --connbytes-mode bytes --connbytes-dir both --connbytes 0:500 \
	-m state --state ESTABLISHED \
	-m length --length 46:375 \
	-m u32 --u32 "\

	""" Simple IPC benchmark test

	Test throughput of 512 KB messages sent between two python processes using:

	- multiprocessing pipe
	- zeroMQ PUSH/PULL
	- zeroMQ DEALER/DEALER

	Result: