Chirag Chamoli chiragchamoli

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

URL	HTTP Verb	Action
/photos/	GET	index
/photos/new	GET	new
/photos	POST	create
/photos/:id	GET	show
/photos/:id/edit	GET	edit
/photos/:id	PATCH/PUT	update
/photos/:id	DELETE	destroy

	# ~/.bashrc: executed by bash(1) for non-login shells.
	# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
	# for examples

	# If not running interactively, don't do anything
	[ -z "$PS1" ] && return

	# don't put duplicate lines in the history. See bash(1) for more options
	# ... or force ignoredups and ignorespace
	HISTCONTROL=ignoredups:ignorespace

	#!/bin/bash

	# Get the path for the .bashrc file from the prompt or set it as being in the users home dir.
	BASHRC="${1:=~/.bashrc}"

	# Use sed to remove the comment from the force color line in the .bashrc file.
	sed -i 's/#force_color_prompt=yes/force_color_prompt=yes/g' $BASHRC

	# BONUS: Uncomment to change the default color of the prompt.
	#sed -i 's/1;32m/1;31m/g'

	---
	# ^^^ YAML documents must begin with the document separator "---"
	#
	#### Example docblock, I like to put a descriptive comment at the top of my
	#### playbooks.
	#
	# Overview: Playbook to bootstrap a new host for configuration management.
	# Applies to: production
	# Description:
	# Ensures that a host is configured for management with Ansible.

	// ==UserScript==
	// @name Translate Amazon
	// @namespace http://your.homepage/
	// @version 0.1
	// @description Translate the Amazon service names into plain English. See https://www.expeditedssl.com/aws-in-plain-english
	// @author @ideasasylum
	// @match https://.console.aws.amazon.com/console/home?
	// @grant none
	// ==/UserScript==

	function slugify(text)
	{
	return text.toString().toLowerCase()
	.replace(/\s+/g, '-') // Replace spaces with -
	.replace(/[^\w\-]+/g, '') // Remove all non-word chars
	.replace(/\-\-+/g, '-') // Replace multiple - with single -
	.replace(/^-+/, '') // Trim - from start of text
	.replace(/-+$/, ''); // Trim - from end of text
	}

	#!/bin/bash
	kill -9 $(ps aux \| grep 'uwsgi' \| awk '{print $2}')
	source /home/ubuntu/.env/myappenv/bin/activate
	cd /home/ubuntu/myapp
	kill -9 $(ps -aux \| grep 'worker.py' \| awk '{print $2}')
	nohup redis-server &
	nohup python -u worker.py > worker.out &
	uwsgi --socket :8881 --plugin python --wsgi-file main.py --callable app --buffer-size 32768 --process 4 --logto /home/ubuntu/myapp/log/myapp.log &

	/**
	* 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).
	*/