5 ms·
Tend to agree (though it's impossible to say about any particular person.) Mentioning TAOCP and SICP at an interview (as he did in the post) would raise some a
by mynameishere 14y ago
Tend to agree (though it's impossible to say about any particular person.) Mentioning TAOCP and SICP at an interview (as he did in the post) would raise some alarms with me. They're not useful books in most jobs, and bringing them up just makes you look like the kind of person who doesn't understand that.
- jarrett 14y agoI see it from another perspective: Mentioning that kind of stuff suggests an appreciation for the finer points of the trade. No, I don't want to work with people who are all theory and no practice. But I do want to work with people who treat coding as more than "copy and paste from Stack Overflow until my boss tells me I'm done."
- eli_gottlieb 13y agoYes, surely we wizards have no desire to leave our big dinners and comfy armchairs at the Unseen University to do any actual magic.
- krmboya 14y agoSteve Yegge calls it "The Awful Place Where People Make Money With Software" http://steve-yegge.blogspot.com/2007/06/rich-programmer-food.html http://steve-yegge.blogspot.com/2007/06/rich-programmer-food...
- papsosouid 13y agoWow, I forgot how horrible he was. How can someone spend that many words just to cough up a few awful strawmen, and then not even bother to knock them down?
- nilkn 13y ago> They're not useful books in most jobs, and bringing them up just makes you look like the kind of person who doesn't understand that. That seems like a rather silly conclusion to draw. I actually think these sorts of hasty conclusions are part of the problem with the hiring process in the industry.
- papsosouid 13y ago>They're not useful books in most jobs Yes, I would certainly question their relevance to most jobs. But we're not talking about most jobs, we're talking specifically about software development jobs. Where they are incredibly useful.