I hereby claim:
- I am evanphx on github.
- I am evanphx (https://keybase.io/evanphx) on keybase.
- I have a public key whose fingerprint is EDFB D4B0 AFF8 4CBA 30F0 8B81 EAE4 8DA5 E365 F367
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
### Keybase proof | |
I hereby claim: | |
* I am seldo on github. | |
* I am seldo (https://keybase.io/seldo) on keybase. | |
* I have a public key whose fingerprint is EBEC BF34 5213 85EF B3D9 B23B 18E9 8404 8E8C C43E | |
To claim this, I am signing this object: |
### Keybase proof | |
I hereby claim: | |
* I am jurvis on github. | |
* I am jurvis (https://keybase.io/jurvis) on keybase. | |
* I have a public key whose fingerprint is 4506 CE5F B766 0FB4 F883 D7A9 B4BA 1210 56E0 19C9 | |
To claim this, I am signing this object: |
#!/bin/bash | |
export PATH=/sbin:/usr/sbin:$PATH:~/.bin:/usr/local/bin | |
# For Skype to recognize desktop themes | |
QT_PLUGIN_PATH=${QT_PLUGIN_PATH+$QT_PLUGIN_PATH:}`kde4-config --path qtplugins` | |
export QT_PLUGIN_PATH | |
if test -z "$XDG_DATA_DIRS"; then | |
XDG_DATA_DIRS="`kde4-config --prefix`/share:/usr/share:/usr/local/share" |
I hereby claim:
To claim this, I am signing this object:
Deep dependencies (npm style) are great when (1) you are relatively memory/bandwidth unconstrained, and (2) your programming style is purely functional. (1) is pretty obvious, so I want to elaborate on (2):
With an object-oriented programming style, you are often passing around instances of your class.
var widget = new Widget
widget.groupWith(otherWidget)
You clearly don't want widget
to interact with slightly different versions of itself through otherWidget
. (Trying to do so would require that we are extremely disciplined with what the Widget::groupWith
method calls on otherWidget
.) Asking for this to work is, in my opinion, a fundamentally bad idea from an architectural point of view. Ideally, it should not be possible for two versions of the Widget
class to exist in the same app. Bundler on Ruby enforces this, and it's awesome.
module Chain where | |
import Data.Map.Strict(Map,insertWith,empty,member,(!)) | |
import System.Random(randomRIO) | |
data Chain = Chain (Map String [String]) Int deriving (Show) | |
build :: [String] -> [String] -> Chain -> Chain | |
build [] _ chain = chain | |
build [_] _ chain = chain |
### Keybase proof | |
I hereby claim: | |
* I am sarajo on github. | |
* I am sara (https://keybase.io/sara) on keybase. | |
* I have a public key whose fingerprint is 00C9 1312 DCA3 A128 9169 9722 5635 BBA2 3F40 6AFF | |
To claim this, I am signing this object: |
I hereby claim:
To claim this, I am signing this object:
General key themes:
Hiring is really hard. You’re not just hiring a “Rails Engineer” or a “Python Programmer” you’re hiring someone who can help you change the world. Tell them why! Talk about the hard problems you’re solving. 2/3 of these talks give ideas and insight into hiring from sourcing to actual interview processes.
Rewriting systems is hard. People think they are going to replace their broken down horse and buggie with a bullet train and this often ends up in disaster. Successful rewrites require an incremental approach that takes months/years and often runs way over schedule. 2/3 of these talks go over how to handle rewrites not only from a high level technical perspective but a cultural/management perspective as well.