Live data from Hacker News

What if we hired writers like we hire developers

hitesh.in

21–30 of 97 posts

Re: What if we hired writers like we hire developers

#21
I'm a professional writer; i.e., I get paid to write. I didn't study journalism but I was in an interdisciplinary programme that consisted of literature, history, and language (somewhat of a modern day philology degree) in Canada. I've just recently started to learn how to program.

I think if this hiring process works for you, great! But as someone who recently started learning to program, I must say writers are vastly different from developers.

There are different kinds of writing. A novelist and a poet (and maybe even an essayist) cannot write business letters. Business writing is vastly different from any creative writing, an SEO writer is neither a creative writer nor a business writer, and so on and so forth. The difference between business writing and creative writing is each follow different rules. That is, each discipline gets away with different things. Creative writing exploits language any which way possible to get a point across, even if it means breaking the rules. Business writers are conservative writers. They follow grammar rules closer, as well as orthography. Most contemporary creative writers use post-structuralist techniques when telling a story; e.g., levels of narration that go from a protagonist to a secondary character to the world in which the book takes place to a far more omniscient narration and much more (narrative modes can get extremely complex). And if they don't, it is almost a given that a type of meta analysis of it is acceptable and encouraged (nowadays, especially). I don't mean to be condescending but business writers use a more primitive form of writing: straight to the point, the nitty-gritty, the meat of the matter. Business writers specialize in a different form of writing. They have more in common with journalists in that they do not exploit language, but seek the simplest form to explain a concept and be completely understood with no room for misinterpretation. I've always said half-jokingly that journalists aren't writers, because they deal with facts and events. I say this meaning journalists do not explore the frightening realm of creative writing, they only dabble in it. Few have ventured to write creatively within their pieces or let abstract concepts permeate throughout an entire piece. For me, journalists and business writers are data-driven and are hard empiricists. There is no market for creative journalists in the entire sense of the word "creative". When companies say "creative" they mean "Can you come up with an idea in which our audience is interested?"

The proof is actually in the tasting. You say you ask your potential hires to spell out a word. There is your first mistake. Do you know how many great writers were poor spellers? Rarely have I seen great writers who are also great spellers. Great writers have great ideas. This is why the world invented editors. It is an old cliché, but one that is true. What's more: do you know professors still teach and believe this? Right, this isn't Academia, and this brings me to another point. Those who do not major in journalism learn to write differently. Most of my peers were bad writers, but they might be a perfect match for a business's needs because they abide by the parameters set by the company. This brings me back to the point that in most business settings, people do not want creative writers. They want someone who writes within the parameters the business calls for or the higher-ups assign.

The Oxford comma. How much does a writer gain by knowing a definition of a word? Let me expand on what Richard Feynman said about what things are called: "I learned very early the difference between knowing the name of something and knowing something". Definitions belong to the category of "knowing the name of something". The problem with this type of 'knowledge' is, most of the time, the interviewer, as someone unfamiliar with the mechanics of language, does not have the capability to ask and know what function the comma holds when placed in a list before a coordinating conjunction. You are testing how many words a writer knows. So, you might as well ask what a Harvard comma is, just in case, to test if the hire knows this and many other words. Anybody can be a technical writer. Anybody can learn the simple rules of language enough to convey a comprehensible idea.

You're essentially looking for a person who fits your idea of a good writer, which should be understood as being a subjective notion. You have a process for knowing who can write best sellers? What are you waiting for? There is lots of money you can be making and, as I'm sure you are a man of science, you can test your hypothesis of being able to pump out best-selling writers.

Seriously. No. Writing a best seller is a completely different ball game, but please feel free to prove me wrong by giving me some results.

Also, I'd just like to clarify that I've not even touched upon the nuances and differing grammar rules from the US, Canada, Australia, and the UK. Suffice it to say that comma splices are not always incorrect depending on where you live and there are different rules for comma usage.

Also, the Elements of Style is an archaic and misguided book, for the most part. None of my professors ever stressed its importance or use. Unfortunately, I've run out of time and must go now. I wish I could touch on other points!

Sorry for any 'style errors' - I've not proofread this :P

Re: What if we hired writers like we hire developers

#22

This ignores different realities in how programmers and writers work. If you're hiring a writer, you cam ask to see his previous work. Unless he worked for CIA, he can point to books he's written, articles he published etc. You can then read them and that's all you need to make a decision if he's competent enough (you might still interview for cultural fit). If you're hiring a senior engineer that claims he spent las…

If you're hiring a senior engineer that claims he spent last 5 years coding Big Table at Google, you have to take his word for it.

I find this assertion to be virtually nonsensical. I've never met a programmer who hasn't written some code that they could show you, if for no other reason than programmers who are passionate about what they do, usually write at least little programs just for fun. And if I were interviewing a programmer, I'd think twice about hiring one who has so little passion for programming that they'd never written anything just for the pleasure of it.

But let's assume for the moment that there are tons of great programmers who've never taken a class for which they could show their code, nor written any code just to write it: Where I work we have a small programming exercise that we ask applicants to submit for code review before we interview them. This process is much more natural than having people code on a whiteboard, because they can do it at their own rate and with their own tools, without having the stress of having someone look over their shoulder. They can also pay proper attention to issues of style and maintainability of their code. The assignments are also something kind of like the work that one might do in the real world.

Re: What if we hired writers like we hire developers

#24

I'm a professional writer; i.e., I get paid to write. I didn't study journalism but I was in an interdisciplinary programme that consisted of literature, history, and language (somewhat of a modern day philology degree) in Canada. I've just recently started to learn how to program. I think if this hiring process works for you, great! But as someone who recently started learning to program, I must say writers are vast…

woosh

Re: What if we hired writers like we hire developers

#25

I'm a professional writer; i.e., I get paid to write. I didn't study journalism but I was in an interdisciplinary programme that consisted of literature, history, and language (somewhat of a modern day philology degree) in Canada. I've just recently started to learn how to program. I think if this hiring process works for you, great! But as someone who recently started learning to program, I must say writers are vast…

Did you really not get that the OP is a parody? The point is that this is obviously NOT the way to hire writers. The implication then being that it is also not the way to hire programmers, even though, sadly, hiring programers is typically done just that way these days.

Re: What if we hired writers like we hire developers

#26
It looks like it's time to recycle some electrons and post the FAQ that Hacker News readers have helped me put together with their previous thoughtful comments about hiring procedures. There are many discussions here on HN about company hiring procedures. From participants in earlier discussions I have learned about many useful references on the subject, which I have gathered here in a FAQ file. The review article by Frank L. Schmidt and John E. Hunter, "The Validity and Utility of Selection Models in Personnel Psychology: Practical and Theoretical Implications of 85 Years of Research Findings," Psychological Bulletin, Vol. 124, No. 2, 262-274

http://mavweb.mnsu.edu/howard/Schmidt%20and%20Hunter%201998%...

sums up, current to 1998, a meta-analysis of much of the HUGE peer-reviewed professional literature on the industrial and organizational psychology devoted to business hiring procedures. There are many kinds of hiring criteria, such as in-person interviews, telephone interviews, resume reviews for job experience, checks for academic credentials, and so on. There is much published study research on how job applicants perform after they are hired in a wide variety of occupations.

The overall summary of the industrial psychology research in reliable secondary sources is that two kinds of job screening procedures work reasonably well (but only about at the 0.5 level, standing alone). One is a general mental ability (GMA) test (an IQ-like test, such as the Wonderlic personnel screening test). Another is a work-sample test, where the applicant does an actual task or group of tasks like what the applicant will do on the job if hired. Each of these kinds of tests has about the same validity in screening applicants for jobs, with the general mental ability test better predicting success for applicants who will be trained into a new job. Neither is perfect (both miss some good performers on the job, and select some bad performers on the job), but both are better than any other single-factor hiring procedure that has been tested in rigorous research, across a wide variety of occupations. So if you are hiring for your company, it's a good idea to think about how to build a work-sample test into all of your hiring processes.

Because of a Supreme Court decision in the United States (the decision does not apply in other countries, which have different statutes about employment), it is legally risk to give job applicants general mental ability tests such as a straight-up IQ test (as was commonplace in my parents' generation) as a routine part of hiring procedures. The Griggs v. Duke Power, 401 U.S. 424 (1971) case

http://scholar.google.com/scholar_case?case=8655598674229196...

interpreted a federal statute about employment discrimination and held that general intelligence tests used in hiring that could have a "disparate impact" on applicants of some protected classes must "bear a demonstrable relationship to successful performance of the jobs for which it was used." In other words, a company that wants to use a test like the Wonderlic, or like the SAT, or like the current WAIS or Stanford-Binet IQ tests, in a hiring procedure had best conduct a specific validation study of the test related to performance on the job in question. Some companies do the validation study, and use IQ-like tests in hiring. Other companies use IQ-like tests in hiring and hope that no one sues (which is not what I would advise any company). Note that a brain-teaser-type test used in a hiring procedure could be challenged as illegal if it can be shown to have disparate impact on some job applicants. A company defending a brain-teaser test for hiring would have to defend it by showing it is supported by a validation study demonstrating that the test is related to successful performance on the job. Such validation studies can be quite expensive. (Companies outside the United States are regulated by different laws. One other big difference between the United States and other countries is the relative ease with which workers may be fired in the United States, allowing companies to correct hiring mistakes by terminating the employment of the workers they hired mistakenly. The more legal protections a worker has from being fired, the more reluctant companies will be about hiring in the first place.)

The social background to the legal environment in the United States is explained in many books about hiring procedures

http://books.google.com/books?hl=en&lr=&id=SRv-GZkw6...

http://books.google.com/books?hl=en&lr=&id=SRv-GZkw6...

Some of the social background appears to be changing in the most recent few decades, with the prospect for further changes.

http://intl-pss.sagepub.com/content/17/10/913.full

http://www.economics.harvard.edu/faculty/fryer/files/Fryer_R...

http://books.google.com/books?hl=en&lr=&id=frfUB3GWl...

Previous discussion on HN pointed out that the Schmidt & Hunter (1998) article showed that multi-factor procedures work better than single-factor procedures, a summary of that article we can find in the current professional literature, for example "Reasons for being selective when choosing personnel selection procedures" (2010) by Cornelius J. König, Ute-Christine Klehe, Matthias Berchtold, and Martin Kleinmann:

"Choosing personnel selection procedures could be so simple: Grab your copy of Schmidt and Hunter (1998) and read their Table 1 (again). This should remind you to use a general mental ability (GMA) test in combination with an integrity test, a structured interview, a work sample test, and/or a conscientiousness measure."

http://geb.uni-giessen.de/geb/volltexte/2012/8532/pdf/prepri...

But the 2010 article notes, looking at actual practice of companies around the world, "However, this idea does not seem to capture what is actually happening in organizations, as practitioners worldwide often use procedures with low predictive validity and regularly ignore procedures that are more valid (e.g., Di Milia, 2004; Lievens & De Paepe, 2004; Ryan, McFarland, Baron, & Page, 1999; Scholarios & Lockyer, 1999; Schuler, Hell, Trapmann, Schaar, & Boramir, 2007; Taylor, Keelty, & McDonnell, 2002). For example, the highly valid work sample tests are hardly used in the US, and the potentially rather useless procedure of graphology (Dean, 1992; Neter & Ben-Shakhar, 1989) is applied somewhere between occasionally and often in France (Ryan et al., 1999). In Germany, the use of GMA tests is reported to be low and to be decreasing (i.e., only 30% of the companies surveyed by Schuler et al., 2007, now use them)."

Re: What if we hired writers like we hire developers

#27

This ignores different realities in how programmers and writers work. If you're hiring a writer, you cam ask to see his previous work. Unless he worked for CIA, he can point to books he's written, articles he published etc. You can then read them and that's all you need to make a decision if he's competent enough (you might still interview for cultural fit). If you're hiring a senior engineer that claims he spent las…

If you're hiring a senior engineer that claims he spent last 5 years coding Big Table at Google, you have to take his word for it. I find this assertion to be virtually nonsensical. I've never met a programmer who hasn't written some code that they could show you, if for no other reason than programmers who are passionate about what they do, usually write at least little programs just for fun. And if I were interview…

I write lots of code just for the sheer pleasure of it. None of it is publicly available though nor would I like to share it. Shipping code is a lot of work. The other day I wrote a quick app at my end to analyze and make sense of some parts of a project that I am about to take on. It does what it needs to but if I had to ship it, I would want to proof read it and describe it's purpose to a general audience and make it at least general enough to have some utility outside my immediate needs. That's a lot of work. I write a lot of code for fun and profit. Writing code and publishing/sharing code are two very different things.

Re: What if we hired writers like we hire developers

#29

This ignores different realities in how programmers and writers work. If you're hiring a writer, you cam ask to see his previous work. Unless he worked for CIA, he can point to books he's written, articles he published etc. You can then read them and that's all you need to make a decision if he's competent enough (you might still interview for cultural fit). If you're hiring a senior engineer that claims he spent las…

In addition I would tend to ask a few important questions of developers:

1) Tell me about one case where you came back to code you had previously written and decided you didn't like the style. What was the issue? Did you rewrite it to fix it? Why or why not?

2) Tell me about one case where you departed from general design best practices where it worked. What did you do? Why did it work well?

3) Tell me about your commenting style. Why and how do you comment your code?

Oh and asking to see code samples is a good thing :-)

Re: What if we hired writers like we hire developers

#30

> Good spellings and knowledge of grammar rules does not indicate a good writer, and there are tools (spelling/grammar check) and (editorial) processes to take care of that. Good grammar doesn't indicate a good writer, but bad grammar does indicate a bad one[1]. (Good grammar meaning, in this case, an ear for language. Good writers avoid grammatical errors because grammatical errors sound wrong , like an off-pitch no…

There are times when good writers use "bad grammar," though. More often though it's "good grammar in a non-standard dialect."
Post reply on HN