$ brew install ansible # OSX
$ [sudo] pip install ansible # elsewhere| #!/usr/bin/python2 | |
| """ | |
| Use scapy to modify packets going through your machine. | |
| Based on nfqueue to block packets in the kernel and pass them to scapy for validation | |
| """ | |
| import nfqueue | |
| from scapy.all import * | |
| import os |
| // CSS Color Names | |
| // Compiled by @bobspace. | |
| // | |
| // A javascript object containing all of the color names listed in the CSS Spec. | |
| // This used to be a big array, but the hex values are useful too, so now it's an object. | |
| // If you need the names as an array use Object.keys, but you already knew that! | |
| // | |
| // The full list can be found here: https://www.w3schools.com/cssref/css_colors.asp | |
| // Use it as you please, 'cuz you can't, like, own a color, man. |
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