Based on a tweet by @Tomwillfixit
Just a quick fun conversion to make it work as a Docker CLI plugin
To use it (assuming you're running a beta of Docker 19.03):
| public class PrintUserHome { | |
| public static void main(String[] args) { | |
| System.out.println("User home: '" + System.getProperty("user.home") + "'"); | |
| } | |
| } |
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
| <html> | |
| <head> | |
| <meta http-equiv="content-type" content="text/html; charset=UTF-8"> | |
| <title>Trello Estimation Timelines</title> | |
| <style type="text/css"> | |
| body { | |
| font-family: arial; |
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
The Gist has been converted to a GitHub repo at https://github.com/gesellix/drone-stack.
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <stdint.h> | |
| #ifdef _MSC_VER | |
| #include <intrin.h> /* for rdtscp and clflush */ | |
| #pragma optimize("gt",on) | |
| #else | |
| #include <x86intrin.h> /* for rdtscp and clflush */ | |
| #endif |
A script that inspects the DNS TTL for a JVM in a supplied Docker image. The image must also contain a JDK.
It does this by generating a Docker image containing a Java program that outputs the JVM's DNS TTL and executing this, then cleaning up the container, image and temporary files.
$ ./jvm-dns-ttl-policy.sh openjdk:8
| #!/usr/bin/python | |
| from subprocess import check_output as run | |
| import glob | |
| # Get nodes | |
| nodes = run(['docker', 'node', 'ls', '-q']).split() | |
| self = run(['docker', 'node', 'inspect', 'self', '--format={{.ID}}']).strip() | |
| nodeinfo = {} |