migurski

#!/usr/bin/env python
''' Convert a series of PNG images to a sparse bundle disk image.

Image file names are passed in as command line arguments.

Example:
    ls *.png | xargs deimgify.py
    
Output:
    Goodtimes.sparsebundle/Info.bckup

indirect

#!/bin/bash

# I alias this script to `mux`:
#   $ alias mux=tmux-named
# Then I tell terminal to automatically attach new windows to my session named "main",
# by setting the preference named "Shells open with" to this command:
#   /path/to/tmux-named main
#
# When working on a particular project, I can jump a session for that project
# by running "mux project-name".

gigamonkey

Links

https://medium.com/@jocelyngoldfein/how-to-hire-engineers-step-0-what-to-look-for-85ae44bf0a1c
http://bryce.vc/post/18018734466/talk-to-us-about-your-problems
https://www.quora.com/Management/What-are-common-mistakes-that-new-or-inexperienced-managers-make/answer/Elaine-Wherry?srid=Q&share=1
http://www.nytimes.com/2011/03/13/business/13hire.html?ref=homepage&src=me&pagewanted=all
http://www.ewherry.com/2012/06/the-recruiter-honeypot/
http://www.ewherry.com/2012/08/the-best-recruiters-followup/
http://randsinrepose.com/archives/the-old-guard/
http://www.humansofnewyork.com/post/108853481056/after-our-first-meeting-ms-lopez-invited-me-to

gigamonkey

• Tell me about your best manager and your worst manager and what made them so.

• Tell me about people you’ve loved working with.

• Tell me about the kind of projects you really love, and projects that drag you down.

• Tell me what I can be doing to support your reaching the next step in your career.

gigamonkey

Books

Algorithms and Data Structures

The Art of Computer Programming (Knuth)

Programming Pearls (Bentley)

Data Structures and Algorithms (Aho, Hopcroft, Ullman)

jvns

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

hellerbarde

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs