Kiln Harmony won't save as much money and angst as a DVCS that automatically converts tabs to spaces and back, based on personal settings, or one that changes bracket code formatting, but it's a start.
Fog Creek Software is hiring full time developers, sales positions, and we're open to looking at intern resume's for summer 2012.
http://www.fogcreek.com/careers.html
I would agree. Though C is far from useless, it really isn't used here at the Creek. Which was a double bonus for me, since after 6 years immersed in C and C++ I could find a job that let me do something new but that I felt very comfortable interviewing for. That said, I really don't believe you need lots of C experience to do well in our interviews.
You're totally right on the path to the source code. The build scripts, as typically run by a developer, should actually do two things: 1) build the code into binaries and 2) deploy those binaries on the developers machine so he/she can easily test it. Builds on official build machines shouldn't be putting the builds into the hard coded location, and so shouldn't do the second thing. I haven't started discussing the difference between build scripts and deploy scripts, but that's essentially the difference I'm referring to here.