Andy Lester

Not really relevant to the current topic of Pandora's relationship to music, but for those interested in the historical problem with music (and the music industry), I strongly recommend reading "The Problem With Music" by Steve Albini (From The Baffler, No. 5, 1993)[1]. This was my first introduction to The Baffler, and led me to start reading their publications regularly. I don't always agree with the author's point of view, but almost always find the content stimulating. [1]: http://www.petdance.com/actionpark/albini/the-problem-with-music.html

I've got three good old fashioned book recommendations: * Johanna Rothman's "Hiring Geeks that Fit" (https://leanpub.com/hiringgeeks) does what it says on the tin - her blog is a useful resource too http://www.jrothman.com/blog/htp/ * Andy Lester's "Land the Tech Job You Love" (http://petdance.com/book/) is written for job seeker - but is actually a good read for folk on the recruiting side too [bias warning: I was one of Andy's tech reviewers on this book] * Lou Adler's "Hire With Your Head" which completely changed my approach to interviewing for the better and made it vastly more effective. His accomplishment based interviewing technique is very effective in my experience.

Please remember that a GitHub account is the start of a portfolio, but only a start. You must have some sort of curated guide that will help the reader through the morass of stuff in your account. Otherwise, you're leaving it up to chance that the reader will find what you want her to find. http://petdance.com/2011/08/your-github-account-is-not-your-portfolio-…

I like ack better for searching code: http://petdance.com/ack/

See also: http://petdance.com/perl/command-line-options.pdf

My preferred programmers grep: http://petdance.com/ack/ Though rkern is a very clever fellow, and I'm sure grin is sufficiently awesome. I think I'll benchmark the two...I kinda suspect ack is faster, but maybe Python will surprise me (when I used to work in Python a few years ago, I was occasionally disappointed in its performance for tasks like this). Interestingly, grin uses the exact same output format as ack...same colors and all. And, yep, ack is quite a bit faster: $ time ack joe real 0m1.708s user 0m1.308s sys 0m0.348s $ time grin -d .svn joe real 0m6.066s user 0m5.191s sys 0m0.802s Looks like grin is trying to deal with things that ack doesn't (binary files, for example), so perhaps that's a factor. And, of course, grep (when massaged appropriately to make it only search the bits we really want) is faster still: $ time find * -name '.svn' -prune -o -type f -exec grep joe \{\} + real 0m0.412s user 0m0.149s sys 0m0.189s So, theoretically, one could wrap that up in an alias, but ack is sufficiently fast, and does enough other cool tricks that I'll just stick with it.

Ack is a beautiful tool. http://petdance.com/ack/