Mark Bainter mbainter

## vmware-void-fix
#!/bin/bash

# must run as root
if [ $UID != 0 ]; then
  echo "You must be root."
  exit 0
fi

# soft link vmware's init.d scripts to void's runit directory
ln -s /etc/init.d/vmware* /etc/runit/

## assume_role.py
#!/usr/bin/env python

# This is a trick, to output the bash commands we need to run in shell, and just execute this script inside an eval within our shell, so it imports what we need
# Possibly tie this in with https://gist.github.com/mbainter/b38a4cb411c0b5c1bae6 for MFA support
# Will need to durably store MFA access tokens, possibly in some other env vars
# Could also store all different keys/info in different vars, to reuse as needed (lots of env vars though, file may be better)

import os
import sys
import getpass

## 20111011_SteveYeggeGooglePlatformRant.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                mbainter
                / 20111011_SteveYeggeGooglePlatformRant.md
            
            
              Last active
              August 29, 2015 14:19
                — forked from chitchcock/20111011_SteveYeggeGooglePlatformRant.md
            
          
    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

  
## Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

# This configuration requires Vagrant 1.5 or newer and two plugins:
#
#   vagrant plugin install vagrant-hosts        ~> 2.1.4
#   vagrant plugin install vagrant-auto_network ~> 1.0.0
#
# After installation, the following steps will spin up a master and agent that
# can communicate with each other:
	#!/bin/bash

	# must run as root
	if [ $UID != 0 ]; then
	echo "You must be root."
	exit 0
	fi

	# soft link vmware's init.d scripts to void's runit directory
	ln -s /etc/init.d/vmware* /etc/runit/
	#!/usr/bin/env python

	# This is a trick, to output the bash commands we need to run in shell, and just execute this script inside an eval within our shell, so it imports what we need
	# Possibly tie this in with https://gist.github.com/mbainter/b38a4cb411c0b5c1bae6 for MFA support
	# Will need to durably store MFA access tokens, possibly in some other env vars
	# Could also store all different keys/info in different vars, to reuse as needed (lots of env vars though, file may be better)

	import os
	import sys
	import getpass
	# -- mode: ruby --
	# vi: set ft=ruby :

	# This configuration requires Vagrant 1.5 or newer and two plugins:
	#
	# vagrant plugin install vagrant-hosts ~> 2.1.4
	# vagrant plugin install vagrant-auto_network ~> 1.0.0
	#
	# After installation, the following steps will spin up a master and agent that
	# can communicate with each other: