dodger

Fog Creek dev, here - we, too, have had absolutely great hires from less-selective colleges and with not-so-great resumes. But if you're pressed for time and resources and you have to use a heuristic for where to put recruiting efforts, this can be a good one.

This task used to be more distributed over the server-side devs, but having a single release manager who does this most of the time and other people who do it occasionally and/or when the release manager isn't working seems to work well.

Yes, more or less a new branch for each fix. But with git and Kiln, it's really not a drag at all; the merges are generally really easy and mostly performed by our release manager when the card makes it to 'Ready to Merge'.

One time I was talking to a designer about doing it this way. The designer said "Yeah, that's a great way to find a (look of total disdain) _local_maximum_." As usual, some truth to both points of view.

Thanks so much!