Skip to comments.High-tech and Humanity: 'English Majors Are What We're Looking For'
Posted on 07/26/2013 10:40:44 AM PDT by Kaslin
click here to read article
Mwahahaha! I’m finally recognized as relevant!
High-tech has a SERIOUS problem with language/documentation. I’ve been highly-desirable in my industry since I graduated because I do what most IT people don’t: documentation.
My motto: “You can lead an engineer to documentation, but you can’t make him read it.”
Good code is its own best documentation.
As an engineering student I struggled mightily to get past the few Introduction to the humanities required courses in my curriculum. But I did learn one thing - and it sometimes seems that I must be the only one who remembers it now. And that is the etymology of the terms Philosopher and sophistry.
- 1542, earlier sophister (c.1380), from L. sophista, sophistes, from Gk. sophistes, from sophizesthai "to become wise or learned," from sophos "wise, clever," of unknown origin. Gk. sophistes came to mean "one who gives intellectual instruction for pay," and, contrasted with "philosopher," it became a term of contempt. Ancient sophists were famous for their clever, specious arguments.
- O.E. philosophe, from L. philosophus, from Gk. philosophos "philosopher," lit. "lover of wisdom," from philos "loving" + sophos "wise, a sage."
"Pythagoras was the first who called himself philosophos, instead of sophos, 'wise man,' since this latter term was suggestive of immodesty." [Klein]
If you think that's hard, try to make an engineer write it for his last project when he is just begging to start the next one.
"Hi! Would you like me to interpret some 14th century Middle English poetry while you wait for your latte?"
On what planet? Scientists and engineers are eggheads. I was a history major in the 70s. It was a stupid major then, and it's even more stupid now. Learn a real skill, otherwise there is no hope for you.
You're assuming that developers document their code properly.
As someone who scripts in Powershell, I can tell you that while the big code repositories have decent documentation, pseudo-code is almost non-existent in most public repositories.
I spend more time writing pseudo-code for my programmers than I do actually writing documentation. They don't want to do it. They just want me to tell them how to translate it from what the customer wants to how it needs to be coded.
Tell ya who could use some English majors....the MSM.
The writing is BRUTAL out there!
If you work in the IT gutter like me, you’d be lucky if you get to finish a project.
Last time I spoke to my pal a writer at the software company that exported my job to Bangalore, he told me that they were considering to outsource documentation writing to Singapore.
If all you want is a skill, why go to college?
Pure tech writing, yes. I’m a systems engineer first with a BA in English and a graduate certificate in professional writing (post-grad work). I produce about 100 pages of documentation a month for my team. Granted, most of it’s screenshots, but it’s documentation that didn’t exist.
Documenting a program’s functionality for a user is easy to export. Documenting domain structure, services, networks, storage configurations, standards, policies and procedures, etc. is not something that can be outsourced with any efficiency.
There are no English majors any more. Serious literature is deader than a doornail. My tiny clique in college that communicated in Yeats, Pound, and Eliot allusions is a distant memory.
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.
Problem with engineer documentation is that it’s not functional or practical for users. I’m guilty of it myself. I have Visio diagrams, Excel spreadsheets, Word documents with procedures all over my local and network disks. My job is to consolidate it for presentation to our non-technical executives. They love that stuff.
I used to have a haircutter who had a masters degree in History. He wasn’t all that good at cutting hair, but he always had really good stories. :-)
I find it far harder to get engineers to PRODUCE documentation than reading it.
How hard it is too major in English? When its you’re fist language. Arts and cratfts magors is pointless.
That's too bad. Without the passion that stirs the soul with great writing, it's easy to overlook the riches of a liberal arts education. When Steve Jobs unveiled the iPad, he noted that Apple's DNA was not made up of technology alone. "It's technology married with liberal arts, married with the humanities, that yields us the results that make our hearts sing," he said. Jobs was not alone in recognizing that the high-tech employers seek innovators who employ imagination, metaphor and storytelling, all growing from the rediscovery of great works of literature.
Ping for later
Are you pulling our leg, lol?
Ditt here. Documentation, training, and communicating with the end user.
That’s where I come in. heh
A very senior Oracle consultant once said about his new assignment:
“They have all sorts of different systems running here. And as near as I can tell, absolutely none of it is documented. All of the documentation is in the head of an employee named Sri. And, as near as I can tell, if Sri goes out for lunch and gets hit by a bus, this company goes out of business fifteen minutes later.”
“If all you want is a skill, why go to college?”
Football games on Saturday afternoons, beer, keggars, college chicks, college chicks and parties, friends from different places with different viewpoints, intramural sports, some liberal arts knowledge to go with useful skills and knowledge, a four year degree to qualify you for grad school in something that will make you employable for a reasonable income. Proper sentence structure is purely optional. :)
What you really want are people with a double major in Math and English. You want people who can write about something they actually understand.
On a more serious note than my previous post, one reason the humanities are in trouble is because they are overrun with Marxists. History and English departments mostly offer lots of courses on the Marxist-Feminist view of this, that, or the other thing. Genuine scholarship takes a back seat to Political Correctness. I’m very glad that I came through a department that wasn’t like that (over 20 years ago).
People with both skill-sets are not very common. A rounded education once helped it along, but that’s no longer the norm.
Me toooooooo! Loved being an English major, reading books and writing book reports was a blast!
My group did the same. Users rarely had to call to ask how to make something work... it was all covered. We usually only heard something if a bug in the code popped up.
those that don’t know history are condemned to repeat it; we need more of you
Yes... that’s the same MO here.
I was a composition major. I spent more time writing than reading.
Just an observation :)
"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. :-)
“It’s technology married with liberal arts, married with the humanities, that yields us the results that make our hearts sing,”
System documentation is just like blueprints for a construction project like a house or commercial building. The foundation crew, the framing crew, the plumbers, the electricians, drywall, painting, roofing crews; and more; all are following the same blueprints, even if modifications have to be made to the plans during the project.
A software system thrown together without a similar structured project process; without the project documentation created during each phase; without cooperative effort between the various teams and members, without following a cohesive plan and design, is just a tangle of counter-productive trash.
This kind of mindless garbage is why the USA is in a major depression; and is why outsourcing, off-shoring, and bringing in foreign visa workers by the tens of millions, is even a consideration.
I AM one of the geeks. I just happen to have a Bachelor of ARTS degree to my name. My boss ribs me something terrible when I over-write my RCAs and lessons learned, but he appreciates that he can hand them to his superiors and they’ll be accepted without question.
That makes Sri a vary valuable person, and compensated accordingly, no?
I've had two jobs outsourced out from under me. Both times, neither company was all that concerned about documentation. "We need to document this, WBill, but first, you need to fix these 57 other things. Do the docs in your spare time." .....then, all of a sudden, documentation percolated up to the top of the list. Always. "Make two afternoons a week available to do nothing else", and so on.
First time I had it to happen, I said "great", since I don't particularly mind documenting, and I didn't realize what was going on. Second time, I spent lots of afternoons self-documenting on my resume and cover letters. :-)
And here I thought I was the only POSH-head on FR!
I’d always tell people complaining of my documentation, “Of course its hard to read, the code was hard to write.” But that was back in the days of packing assembly code into 64K blocks.
I have that on my coffee mug.
I knew an old electrician who worked in a steel mill here in Pittsburgh. The only documentation for anything in that mill was in his head. In fact he used to memorize blueprints of stuff done before he got the job then he’d burn them.
“Job Security” to the unionized mind.
He’d also help himself to any company property he wanted as an unwritten part of the contract. And he’d come over and rig your cable box to steal HBO for twenty-five bucks.
I’m not good at it, but I use it every day. I wasn’t very good at C in college either, but I struggled through it.
The term, cognitive disconnect, applies to the condition where reality and one's understanding or perception of reality differ.
If a company has American jack-leg coders who cannot (or refuse) to communicate, document, design, and work cooperatively as part of a functioning team, why the heck would they ever hire another illiterate, counter-productive American over a foreign coder who will at least try to read, write, and speak English, and work as part of a team.
I pretty much work out of a PS console and the ISE most of the time. Never had much formal training, but I’ve managed well enough to make a respectable showing that the Scriting Games the last couple of years. I’m an AD/Exchange admin, but I’ve been getting more and more programmers coming to my cube for help with Powershell and regex.