I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
defmodule Curry do | |
defmacro defcurry({func_name, _func_ctx, args}, do: body) do | |
num_args = Enum.count(args) | |
if num_args - 1 >= 1 do | |
new_args = Enum.take(args, num_args - 1) | |
quote do | |
def unquote(func_name)(unquote_splicing(args)) do | |
unquote(body) | |
end |
defmodule Curried do | |
defmacro defc({name, _, args}, [do: body]) do | |
curried_args = Enum.map(Enum.with_index(args), fn({_, index}) -> | |
Enum.take(args, index + 1) | |
end) | |
for a <- curried_args do | |
if a == Enum.at(curried_args, Enum.count(curried_args) - 1) do | |
quote do | |
def unquote(name)(unquote_splicing(a)) do | |
unquote(body) |
I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
{ config, pkgs, ... }: | |
{ | |
imports = [ ./default.nix /root/nixcfg/core.nix ]; | |
services = { | |
example = { | |
enable = true; | |
}; | |
}; | |
environment.systemPackages = with pkgs; [ wget tcpdump ltrace gdb ]; |
#!/bin/bash | |
exec {times}> times {typescript}> typescript < "${1-/dev/stdin}" | |
while read -r; do [[ $REPLY = ' "stdout": [' ]] && break; done # skip to this line | |
LANG=C | |
printf "Script started on %(%c)T\n" -1 >&"$typescript" # dummy | |
while read -r open; [[ $open = '[' ]]; do | |
read -r elapsed; read -r string; read -r close | |
eval printf %b%n "$string" characters >&"$typescript" # put count in $characters | |
printf "%s %s\n" "${elapsed%,}" "$characters" >&"$times" | |
done |
It's a common confusion about terminal colours... Actually we have this:
printf "\x1b[${bg};2;${red};${green};${blue}m\n"
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