chitchcock

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

saetia

OS X Preferences

---

most of these require logout/restart to take effect

# Enable character repeat on keydown
defaults write -g ApplePressAndHoldEnabled -bool false

# Set a shorter Delay until key repeat

jtimberman

# Put this in ~/chef-repo/data_bags/aws/main.rb
# Upload it to the Chef Server with:
#
#   knife data bag item rb aws main.rb
#
# Export the two AWS values for your account.

{
  'id' => "main",
  'aws_access_key_id' => ENV['AWS_ACCESS_KEY_ID'],

smoser

#!/bin/sh
# vi: ts=4 noexpandtab
# rsa2azure

Usage() {
   cat <<EOF
Usage: ${0##*/} [options] [private-key]
   convert private-key in ssh private key format to the format
   needed by windows azure as described at
      http://utlemming.azurewebsites.net/?p=91

jespada

In a perfect world, where things are done well, not just quickly, I would expect to find the following when joining the company:

Documentation

• Accurate / up-to-date systems architecture diagram

• Accurate / up-to-date network diagram

• Out-of-hours support plan

• Incident management plan

piscisaureus

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 = git@github.com: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:

rgreenjr

-- show running queries (pre 9.2)
SELECT procpid, age(clock_timestamp(), query_start), usename, current_query 
FROM pg_stat_activity 
WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' 
ORDER BY query_start desc;

-- show running queries (9.2)
SELECT pid, age(clock_timestamp(), query_start), usename, query 
FROM pg_stat_activity 
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' 

karmi

.vagrant
Gemfile.lock
Berksfile.lock
tmp/

dacort

package main

import (
	"code.google.com/p/go.crypto/pbkdf2"
	"crypto/aes"
	"crypto/cipher"
	"crypto/sha1"
	"database/sql"
	"fmt"
	"log"