csrutil disable
package azurex | |
import ( | |
"context" | |
"errors" | |
"fmt" | |
"os" | |
"strings" | |
"github.com/Azure/azure-sdk-for-go/profiles/2020-09-01/resources/mgmt/subscriptions" |
javascript: Promise.all([import('https://unpkg.com/turndown@6.0.0?module'), import('https://unpkg.com/@tehshrike/readability@0.2.0'), ]).then(async ([{ | |
default: Turndown | |
}, { | |
default: Readability | |
}]) => { | |
/* Optional vault name */ | |
const vault = ""; | |
/* Optional folder name such as "Clippings/" */ |
These notes assume that you already have an app service plan running a number of sites (web apps) that ALL want the same wildcard cert.
The problem being solved was how to point a number of sites to a company domain.
The aliases (e.g. alias trainer.foo-uk.com
onto CNAME pvb-live-eun-trainer-as.azurewebsites.net
) MUST already be configured in DNS -- Azure will check!
''' | |
List all inactive user of a GitHub organization | |
See user.py --help for usage. | |
Partially inspired by https://gist.github.com/morido/9817399 | |
''' | |
import sys # to use sys.stdout | |
import os | |
from datetime import datetime | |
from time import strftime | |
import datetime |
#!/usr/bin/env python | |
# you will need http://github3py.readthedocs.org/en/latest/#installation | |
# I'm not sure if this works on Windows due to the use of strptime() | |
from github3 import login | |
import datetime | |
import json | |
# Amend the following two lines as necessary |
$ ./githubapi-get.sh $GITHUBTOKEN /users/mbohun/repos
HTTP/1.1 200 OK
Server: GitHub.com
Date: Wed, 04 Mar 2015 04:30:29 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 155683
Status: 200 OK
By Steve Yegge
Last week I accidentally posted an internal rant about service platforms to my public Google+ account (i.e. this one). It somehow went viral, which is nothing short of stupefying given that it was a massive Wall of Text. The whole thing still feels surreal.
Amazingly, nothing bad happened to me at Google. Everyone just laughed at me a lot, all the way up to the top, for having committed what must be the great-granddaddy of all Reply-All screwups in tech history.
But they also listened, which is super cool. I probably shouldn’t talk much about it, but they’re already figuring out how to deal with some of the issues I raised. I guess I shouldn’t be surprised, though. When I claimed in my internal post that “Google does everything right”, I meant it. When they’re faced with any problem at all, whether it’s technical or organizational or cultural, they set out to solve it in a first-class way.
Anyway, whenever something goes viral, skeptics start wondering if it was faked or staged. My accident
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,