[tjr]

I once had a job interview for a programming job in which I was asked about the several (programming-related) publications I had listed on my resume.

"Why did you do this? It looks like you want to be a writer, not a programmer!"

I find it hard to imagine being so consumed with programming that you don't do anything else at all, even things that are related to, but not actually, programming. But even harder to imagine is why anyone would expect someone to be that consumed with only programming?

[npsimons]

At my current job, it seems like I am constantly being pressured into being a "systems engineer" or somesuch. The fact of the matter is, I really love writing code, finding and fixing bugs, and just generally all around playing with software. I can appreciate, and am even very interested in, things such as hardware, materials science, physics, chemistry, etc. But there is more than enough for one lifetime (multiple lifetimes!) in software, and I just find it so cool that I don't want to do much else. Don't get me wrong; outside of work I'm an amateur musician and a volunteer SAR member. I also appreciate stretching your mind, getting a different POV and cross-training, etc, etc, but as long as people are willing to pay me to make software, that's the job I'll continue to do. Try to push me into something I'm not interested in, and you'll have to find another code monkey. I'll dive into wildly differing domains, but mainly so I can tackle them better in software.

[johnjlocke]

I would find it off-putting if someone pulled that line on me in an interview too. Being a programmer does not mean that you are a simply a code monkey, incapable of expanding your knowledge of the field.

You would think that all companies would want someone who understood programming enough to be able to write about it in a way that others could understand, but perhaps not. Some places "get it" and some don't.