3 ms·
> Do some research To me, doing research is the lowest hanging fruit with the highest return on investment. From a journalism context, I push students to hit L
by danso 10y ago
> Do some research
To me, doing research is the lowest hanging fruit with the highest return on investment. From a journalism context, I push students to hit LexisNexis and Google hard before they do interviews. Whenever a student complains that they don't have any interesting questions to ask, or the subject had nothing interesting to say, almost always the problem could have been mitigated with pre-interview research.
The benefits of doing research for interviewing:
- You can learn the boilerplate of the subject, which serves the dual purpose of making you more nimble in interpreting the context of responses and saves you from wasting valuable question time of basic info ("So when did you start directing, Mr. Tarantino?)
- You can learn the current or ongoing controversies of a subject, from which almost all interesting questions arise.
- You find other interesting people to interview.
When your questions are derived from research, you save time by cutting through the boilerplate and any bullshit that might be offered as a response. Furthermore, there's an unquantifiable benefit in increasing respect -- that is, your subject will give you more serious, thoughtful answers because they see that you've put serious, thoughtful effort into understanding them.
You can gain this rapport if you're in a position of authority, or have the chance of multiple interviews. But in cases where you're just another possibly-threatening interrogator, doing your research is an easy and accessible way of increasing your authority, and thus, the quality of answers you receive. It can more than make up for in-person skills, depending on the situation and subject.
Edit: the OP suggests not being so strict on Gogling-before-asking, because she likes to ask basic questions during casual conversation, like over lunch/coffee. I think you can have your cake and eat it too. Sometimes I'll ask questions that I already know the answer to, as an icebreaker. But again, this requires research for the domain knowledge. Ideally, you want your icebreaker questions to be one that you anticipate the person is enthusiastic to answer. While they're saying what you think they'll say, you can spend that time gauging the person's mood and think of segues into other lines of questioning. Of course, once in awhile, they'll respond to your softball basic question with something that you didn't expect...and that in itself leads to potential insights.
- LoSboccacc 10y agoas a an usual question answerer, people that come at me without doing basic google research pisses me off to no end and I get super unhelpful if I have to start the explanation from the ice age forward, especially if I'm not in a teaching settings.
- taeric 10y agoAgreed, though this can be easily taken too far [or not far enough... depending how you see it]. I find it helpful to research enough to know the landscape, but not enough to form an opinion. Unless I plan on doing a lot of research to become an expert, I find it easy to form opinions that require massive nuance to matter. Edited to add the [] bracketed part.
- logicallee 10y agoI'm going to completely disagree with you. I've always (WITHOUT EXCEPTION) learned valuable information when I've chosen to ask a basic questions I could have Googled. There is a reason people choose to answer it. Here is a typical basic question anyone could Google: "Could you explain the difference between C-style and C++-style arrays." I guarantee you that the answer is better than the Google search. Now let me search: https://www.google.com/search?q=difference+between+C-style+and+C%2B%2B-style+arrays https://www.google.com/search?q=difference+between+C-style+a... Yep. NOT ONE of the search hresults (I opened about 10) explains what they are, easily. As a quick test, go ahead and ask your coworkers "Could you explain the difference between C-style and C++-style arrays." They are a hundred times more likely to give you better answers. I thought I would be downvoted for this comment so I went ahead and got on IRC. This is the answer I received: hi - could you explain the difference between C-style and C++-style arrays? <[respondent]> C-array is just a pointer to a bunch of values you hopefully know the count of <[respondent]> C++ std::array thing iirc has more type safety That summarizes EVERYTHING. That's literally it. The key, key, key thing "you hopefully know the count of" comes FIRST. It's just a pointer. You hopefully know the count. And then it mentions that this is information which std::array can track. That's it. Try to find anything like those two lines out of all of the links. As far as UNDERSTANDING - as in, if there's a conceptual hurdle, you will never EVER get as easy and quick an understanding as if you ASK someone. NEVER EVER EVER.
- userbinator 10y agoC-array is just a pointer to a bunch of values Unfortunately, that's wrong too. A C array is not a pointer. If you then Google "C array is not a pointer", you will find plenty of results telling you why.