Eamonn Power epower

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

Update HISTORY.md
Commit the changes:

git add HISTORY.md
git commit -m "Changelog for upcoming release 0.1.1."

Update version number (can also be minor or major)

bumpversion patch

Software for scientists

Some things takes much less time and stress once you know the right tool. Below, there is a community edited list of software for scientists.

Text editors

in General purpose text/code editors. It may be better to have a good editor for everything, than different ones for different languages, scripts, notes.

Rich Hickey on becoming a better developer

Rich Hickey • 3 years ago

Sorry, I have to disagree with the entire premise here.

A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.

Mastery comes from a combination of at least several of the following:

Ryan Frantz defined monitoring at http://www.ryanfrantz.com/posts/solving-monitoring/ as

Monitoring is the aggregation of health and performance data, events, and relationships delivered via an interface that provides an holistic view of a system's state to better understand and address failure scenarios.

Here's my alternative definition

Monitoring is the detection of variation outside the steady state of the business.

FINALLY no need for tricks!

bonus tip: for more darkness > https://darkreader.org/

	/**
	* Annoying.js - How to be an asshole to your users
	*
	* DO NOT EVER, EVER USE THIS.
	*
	* Copyright (c) 2011 Kilian Valkhof (kilianvalkhof.com)
	* Visit https://gist.github.com/767982 for more information and changelogs.
	* Visit http://kilianvalkhof.com/2011/javascript/annoying-js-how-to-be-an-asshole/ for the introduction and weblog
	* Check out https://gist.github.com/942745 if you want to annoy developer instead of visitors
	*

	#!/usr/bin/env python

	"""
	Ubuntu MaaS External Inventory Script for MaaS Tower
	====================================================

	This script fetches hosts data for Ansible from Ubuntu MaaS, using Tags to identify groups and roles. It is expected
	that the script will be copied to Tower within the new Inventory Scripts dialog offered within the interface, where
	it will be passed the `--list` argument to invoke the dynamic inventory process.

	CMDB:
	I do not have names on specific commentors. These notes have been re-ordered to make a bit more sense.

	We have dynamic environments, with information coming from systems and builds.
	Systems need configuration from runtime data based on service discovery and build configuration (IP addresses, versions, etc).

	CMDB use contexts:
	On call users - The sysadmin who has been paged at 4 am needs to determine context for the page.
	Deployment systems - To know where to deploy software, what version(s) to deploy, etc.
	Maintenance - Downtimes, escalate, software versions, hardware info...