Append this to your ~/.zshrc file.
function preexec() {
timer=$(($(date +%s%0N)/1000000))
#!/bin/bash | |
ADBShell () { adb ${2+-s }$2 shell "$1" | tr -d '\r' | |
} | |
GetAndroidVersion () { | |
local ALL_TAGS=$(wget -qO - "$GOOGLE_SOURCE/$REPO/+refs/tags/?format=text" | \ | |
tr -d '^{}' | cut -d/ -f3 | sort -u | grep -vE -- '-(cts|sdk)-' | grep -v "_r0") | |
TAG=${1:-$(ADBShell 'getprop ro.build.version.release')} | |
echo -e "ANDROID_SERIAL=$ANDROID_SERIAL\nro.build.version.release=$TAG" 1>&2 |
vi /etc/environment | |
add these lines... | |
LANG=en_US.utf-8 | |
LC_ALL=en_US.utf-8 |
javascript: | |
document.querySelectorAll('.load-diff-button').forEach(node => node.click()) |
# Generate the private and public keys | |
openssl ecparam -name secp256k1 -genkey -noout | openssl ec -text -noout > key | |
# Extract the public key and remove the EC prefix 0x04 | |
cat key | grep pub -A 5 | tail -n +2 | tr -d '\n[:space:]:' | sed 's/^04//' > pub | |
# Extract the private key and remove the leading zero byte | |
cat key | grep priv -A 3 | tail -n +2 | tr -d '\n[:space:]:' | sed 's/^00//' > priv | |
# Generate the hash and take the address part |
#!/usr/bin/env node | |
'use strict'; | |
// ethereum: generate signed transactions | |
const fs = require('fs-extra'); | |
const rls = require('readline-sync'); | |
const Accounts = require('web3-eth-accounts'); | |
const web3utils = require('web3-utils'); | |
const accounts = new Accounts(); |
#!/bin/bash | |
#### Default Configuration | |
CONCURRENCY=4 | |
REQUESTS=100 | |
ADDRESS="http://localhost:8080/" | |
show_help() { | |
cat << EOF |
#!/usr/local/bin/python3 | |
# -*- coding: utf-8 -*- | |
from __future__ import print_function | |
import redis | |
import json | |
import time | |
from itertools import zip_longest | |
from clint.arguments import Args |
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 really have SREs and they make engineers pretty much do everything,
{ | |
"point_left": "\ud83d\udc48", | |
"mailbox_with_mail": "\ud83d\udcec", | |
"timer": "\u23f2", | |
"grinning": "\ud83d\ude00", | |
"yum": "\ud83d\ude0b", | |
"strawberry": "\ud83c\udf53", | |
"ice_skate": "\u26f8", | |
"middle_finger_tone2": "\ud83d\udd95\ud83c\udffc", | |
"star_and_crescent": "\u262a", |