ssh-keygen -t ed25519 -C "user@email.com" -f ~/.ssh/id_rsa_github
ssh-keygen -t ed25519 -C "user@email.com" -f ~/.ssh/id_rsa_gitlab
Discover gists
23.21.150.121:3478 | |
iphone-stun.strato-iphone.de:3478 | |
numb.viagenie.ca:3478 | |
s1.taraba.net:3478 | |
s2.taraba.net:3478 | |
stun.12connect.com:3478 | |
stun.12voip.com:3478 | |
stun.1und1.de:3478 | |
stun.2talk.co.nz:3478 | |
stun.2talk.com:3478 |
#!/bin/bash | |
# | |
# Generates thumbnail contact sheets of all video files in current working directory. | |
# | |
# Script defaults to writing PNG contact sheets to the same folder, using the original | |
# video filename as the basename for the contact sheet | |
# | |
# More details: https://trac.ffmpeg.org/wiki/Create%20a%20thumbnail%20image%20every%20X%20seconds%20of%20the%20video | |
# | |
# NOTE: 'montage' requires that Ghostscript be installed, in order to be able to generate titles |
NOTICE: This guide will help you set ssh keys for GitHub and GitLab. However, this is not going to change your commit
user.name
oruser.email
. If you need to change those for specific repositories, just run the following commands while in your repository:
git config user.name "Your Name Here"
git config user.email your@email.com
For more info, see this answer. Also, keep in mind this only changes the
.git
folder inside your repository which never gets added/committed/pushed/uploaded.
I recently had to manage two ssh keys (one for Github and one for Gitlab). I did some research to find the best solution. I am justing putting the pieces together here.
if ('WebSocket' in window) { | |
(function () { | |
function refreshCSS() { | |
var sheets = [].slice.call(document.getElementsByTagName("link")); | |
var head = document.getElementsByTagName("head")[0]; | |
for (var i = 0; i < sheets.length; ++i) { | |
var elem = sheets[i]; | |
var parent = elem.parentElement || head; | |
parent.removeChild(elem); | |
var rel = elem.rel; |
1 | LAFBD-41 | |
---|---|---|
2 | SSNI-497 | |
3 | ABP-984 | |
4 | IPX-580 | |
5 | IPX-811 | |
6 | IPX-177 | |
7 | STARS-804 | |
8 | SMBD-115 | |
9 | ABP-968 | |
10 | ABF-017 |
#!/usr/bin/env python | |
# -*- coding: utf-8 -*- | |
import sys | |
import numpy | |
import OpenEXR | |
import Imath | |
import Image |
This is not an exhaustive list of all interfaces in Go's standard library.
I only list those I think are important.
Interfaces defined in frequently used packages (like io
, fmt
) are included.
Interfaces that have significant importance are also included.
All of the following information is based on go version go1.8.3 darwin/amd64
.
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