Nathan Weddle nweddle

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

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2:

When you do your first Sonar run on your project, you get a lot of new quality numbers to play with, but no trends. You only have one data set for comparison, the now picture.

Wouldn't it be nice if you could see the current trend of the project without waiting a couple of month for the 'daily/weekly' Sonar runs to fill up the data? Well, you're in luck! And if you're using git as a version system as well, this is your day. :)

In the Sonar Advanced Parameter documentation you will find a System Property called sonar.projectDate. The property let you tell Sonar when in time the running analysis was ran.

By combining this property and what your version system does best, track changes to source, we can now play back the history of the project as far as Sonar is concerned.

This little Bash script illustrates the concept. To spell out what it does in human readable form:

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

	#!/bin/bash
	#
	# Open new Terminal tabs from the command line
	#
	# Author: Justin Hileman (http://justinhileman.com)
	#
	# Installation:
	# Add the following function to your `.bashrc` or `.bash_profile`,
	# or save it somewhere (e.g. `~/.tab.bash`) and source it in `.bashrc`
	#

	namespace :ec2 do
	# setup chef config
	#
	config = File.join(File.dirname(__FILE__), '..', '.chef', 'knife.rb')
	Chef::Config.from_file(config)

	load_gem_or_report(%w{aws})

	desc 'Delete any ec2-based chef nodes that no longer exist'
	task :cleanup_nodes do

	#!/usr/bin/ruby
	require 'rubygems'
	require 'hipchat-api'
	require 'getopt/long'
	require 'socket'
	require 'erb'

	#Do not modify these constants! (after you set these up, of course)
	HipApiKey='ABCDEFGHKJHKJHKJHKJH'
	Room='Nagios'

	C:
	cd %WINDIR%\Microsoft.NET\Framework\
	for /d %%D IN (*) DO .\%%D\ngen.exe executeQueuedItems

	cd %WINDIR%\Microsoft.NET\Framework64\
	for /d %%D IN (*) DO .\%%D\ngen.exe executeQueuedItems
	pause

	<powershell>

	# First we add our administrative user, replace username and password with your own
	$computer=$env:ComputerName
	$user="username" ## Change this!
	$password='password' ## And change this too!
	$objOu = [ADSI]"WinNT://$computer"
	$objGroup = [ADSI]"WinNT://$computer/Administrators,group"
	$objUser = $objOU.Create("User", $user)
	$objUser.setpassword($password)