This gist is part of a blog post. Check it out at:
http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
#!/usr/bin/perl | |
# CouchDB Tunnel Tool for MacOS X and Linux | |
# Copyright (c) 2010 Linode, LLC | |
# Author: Philip C. Paradis <[email protected]> | |
# Modifications: Sam Kleinman <[email protected]> | |
# Usage: couchdb-tunnel.pl [start|stop] | |
# Access a CouchDB database instance by way of an SSH tunnel. | |
## |
# Install Erlang | |
$ sudo apt-get install autoconf | |
$ curl -O https://raw.github.com/dreverri/kerl/master/kerl; chmod a+x kerl | |
$ ./kerl build R14B03 r14b03 | |
$ ./kerl install r14b03 /opt/erlang/r14b03 | |
$ . ~/.kerl/installs/r14b03/activate | |
# Build Riak from source | |
$ git clone git://github.com/basho/riak.git | |
$ cd riak |
%!TEX TS-program = xelatex | |
\documentclass[12pt]{scrartcl} | |
% The declaration of the document class: | |
% The second line here, i.e. | |
% \documentclass[12pt]{scrartcl} | |
% is a standard LaTeX document class declaration: | |
% we say what kind of document we are making in curly brackets, | |
% and specify any options in square brackets. |
This gist is part of a blog post. Check it out at:
http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
#################################### | |
# BASIC REQUIREMENTS | |
# http://graphite.wikidot.com/installation | |
# http://geek.michaelgrace.org/2011/09/how-to-install-graphite-on-ubuntu/ | |
# Last tested & updated 10/13/2011 | |
#################################### | |
sudo apt-get update | |
sudo apt-get upgrade |
#!/usr/bin/env python | |
""" | |
ODT2PANDOC | |
========== | |
ODT2PANDOC is a slight variant of ODT2TXT. Right now, the only differences are that it generates ATX style headers and uses *asterisks* for italics, neither of which is in any way specific to pandoc's extended markdown. | |
ODT2TXT | |
======= |
# args is sys.argv[1:] | |
def foo(config, args): | |
config.domain = None | |
config.fullurl = None | |
hostname = None | |
it = iter(args) | |
while True: | |
try: | |
arg = next(it) |
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
{%- macro form_field_label(field) -%} | |
<label for="{{ field.id }}">{{ field.label.text }} | |
{%- if field.flags.required -%} | |
<abbr title="Diese Feld muss angegeben werden">*</abbr> | |
{%- endif %}</label> | |
{% endmacro %} | |
{%- macro form_field_description(field) -%} | |
{% if field.description %} | |
<span class="descr">{{ field.description }}</span> |