Marty Phee martyphee

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

	/**
	* Fancy ID generator that creates 20-character string identifiers with the following properties:
	*
	* 1. They're based on timestamp so that they sort after any existing ids.
	* 2. They contain 72-bits of random data after the timestamp so that IDs won't collide with other clients' IDs.
	* 3. They sort lexicographically (so the timestamp is converted to characters that will sort properly).
	* 4. They're monotonically increasing. Even if you generate more than one in the same timestamp, the
	* latter ones will sort after the former ones. We do this by using the previous random bits
	* but "incrementing" them by 1 (only in the case of a timestamp collision).
	*/

	"""
	This is an extension of the technique first detailed here:

	http://sedimental.org/remap.html#add_common_keys

	In short, it calls remap on each container, back to front, using the accumulating
	previous values as the default for the current iteration.
	"""

	// val ZIOVersion = "1.0.0-RC17+319-8917936d-SNAPSHOT"
	// resolvers += Resolver.sonatypeRepo("snapshots")
	//
	// libraryDependencies ++= Seq(
	// // zio
	// "dev.zio" %% "zio" % ZIOVersion,
	// "dev.zio" %% "zio-streams" % ZIOVersion,
	// )

	/**
	* Interceptor
	* Implements functionality to catch various requests and fire events when they happen. This is generally to ensure
	* that responses from the server are handled in a uniform fashion across the application. Also, by firing events
	* it allows to have any number of handlers attach to the response.
	*
	* @author Kirk Bushell
	* @date 28th March 2013
	*/
	var module = angular.module('core.interceptor', []);