The old problem with software documentation is that it’s written by documentation writers, and not by the engineers who write the code, and are typically inarticulate, impatient and secretive when interviewed by the writers. In my career, writing code for internal use (by those same engineers, by the way) we wrote our own documentation, and it was better than any published docs I had ever seen, including the docs for use by the company customers. Our motivation was simple: we didn’t want to explain ourselves over and over again. RTFM was our usual answer.

"You can lead an engineer to documentation, but you can't make him read it!" classic..

To be certain, we don't like to write stuff down. And reading docs is for wimps. "Hell, no, I didn't read it! Let's fire this baby up, and see what happens!!!!" :-)

However, I'd argue that it's hard to find an English major (recent grad) who can keep up with Engineers. They're certainly better than anything with "Studies" in it, because I'd assume that an English Major at least would be able to read and write English. "Studies" majors? Not so much.

So, if you're technical enough to hang with the geeks, and literate enough to communicate well....you're one of a rare breed, indeed. :-)