kerneltime

Keybase proof

I hereby claim:

• I am kerneltime on github.
• I am kerneltime (https://keybase.io/kerneltime) on keybase.
• I have a public key ASAY_vmvboJjlTaH7OaCG0GiJqoC_8Qxhww0emLFEFt5ygo

To claim this, I am signing this object:

kerneltime

PostgreSQL & PostGIS Cheatsheet

This is a collection of information on PostgreSQL and PostGIS for what I tend to use most often.

TOC

• Installing Postgres & PostGIS
• Using Postgres on the command line: PSQL
• Importing Data into Postgres
• Exporting Data from Postgres
• Joining Tables

kerneltime

Keybase proof

I hereby claim:

• I am kerneltime on github.
• I am kerneltime (https://keybase.io/kerneltime) on keybase.
• I have a public key ASAIjTF8nhsFI56_cUPordnfk3FiC0Efn_0cP3Jx4Ve62Qo

To claim this, I am signing this object:

kerneltime

• A stateful set implementing S3 compatible service gets a DNS name such as: ${S3 instance}.${namespace}.svc.cluster.local

  • APIs such as list bucket and make bucket are sent to this DNS address

• Buckets in S3 have their own DNS name and going forward it is the preferred way for communicating with a bucket. (vs path style)

• We can create a new service per bucket (backed by the stateful set) and give it a DNS name ${bucket}.${namespace}.svc.cluster.local. It is mapped to the Stateful Set via Cluster IP.

  • To be compatible with S3 style DNS we need: ${bucket}.${S3 instance}.${namespace}.svc.cluster.local
  • Currently a service name cannot have a “.” in their name.

kerneltime

curl -Ol https://golang.org/src/crypto/tls/generate_cert.go
go run generate_cert.go -ca --host "192.168.86.47"
cp cert.pem key.pem ~/.minio/certs
mv ~/.minio/certs/cert.pem ~/.minio/certs/public.crt
mv ~/.minio/certs/key.pem ~/.minio/certs/private.key
> cat start-https.sh 
export MINIO_ACCESS_KEY="minio"
export MINIO_SECRET_KEY="minio123"
export MINIO_PROMETHEUS_AUTH_TYPE="public"

kerneltime

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