Tag Archives: Employment

The Question of Code Revisited: I Think I Can, So Can’t I?

#sci4hels, Employment, Jobs, Science writing, State of Journalism,

“All of the true things I’m about to tell you are shameless lies.” Is it ever acceptable to walk into an interview with a mentality straight out of the Books of Bokonon from Kurt Vonnegut’s Cat’s Cradle? In addition to being what is possibly my favorite literary quote ever, I think the idea of telling true lies really epitomizes an issue that so many science writers trying to break into the business are facing: when asked what our skills are, is what we feel comfortable knowing, all that we really know? 

 I’ve been turning this over in my brain for a couple of months now. In September I wrote a blog post about whether or not learning to code should be required for journalists. Since I admittedly can’t code, I took the position that it doesn’t need to be required. I also said that in interviews it is totally unacceptable to claim that you can code when you can’t. I didn’t expect that statement to be a part of the post that would get any discussion going, but as it turned out it became for me the most interesting part. When the #sci4hels got talking about it, what seemed like a black and white issue (of course you shouldn’t stretch the truth in an interview!) became a lot less clear and a lot more complicated.

Degrees of truth

A lie is a lie, right? As journalists don’t we value the implicit requirement of honestly above nearly all else? Doesn’t this extend from what we say in a piece to the way we conduct ourselves professionally? So then, can you sit in an interview and when asked if you can code, edit video, make a podcast, etc. say that you can when you’ve never done it before? Is the skill that you have the ability to code or is the skill that you have the ability to learn to code? Learn quickly. In a way so that your potential employer never finds out that the moment you told them you could code you actually couldn’t. Is stretching the truth about your abilities lying? Even if it is lying, is it wrong or is it just a smart business move?
 
For me, the idea of claiming to know code when I don’t is absurd. Mostly because I don’t stand a chance of learning code in the time between getting hired and needing to use it on a professional level. I know, I know code isn’t THAT hard. I’ve heard that argument, the “you can do if you try” talk. I’m not scared to try, I just know myself enough to know that I’m not going to learn to code in a day. It took several weeks of my seventh grade school year for the Pythagorean theorem to make sense, and that’s not exactly hard. I try, but I’m not always a quick study. Maybe as far as being a millennial goes this puts me in the minority, but I know that if I sat in an interview and promised to code at a professional level in a days time I’d be telling a Vonnegut style shameless lie.
Why was this the bane of my middle school existence? Via Wikimedia Commons

Why was this the bane of my middle school existence? Via Wikimedia Commons

But, I’m not everybody. If the light bulb in your brain turned on a little bit faster when you were twelve and learning that a² + b² = c² then maybe you can learn to code in a day. Maybe code is the most logical thing you’ve ever seen and you will be its master by dinnertime. If you tell a potential employer that you can code, and you are completely sure of your ability to be able to deliver when called upon to use those skills, are you telling a lie? Is knowing what you need to know in order to know how to code the same as just knowing how to code?

 
I said before that I wasn’t afraid of code, but by sitting in an interview and swearing to the things I can’t do, am I selling myself short? Some of us might just be hiding behind a list of things we can’t do or won’t do and simultaneously shrinking our career prospects. Self sabotage, as it were. Is it principled, or pathetic? Being honest might be a one way ticket straight to the rejection pile. If I communicate the fact that I’d like to learn to code, and would gladly rise to that challenge enough to make someone want to hire me?

I have no faith in common sense

How do you know whether what you know is enough to claim that you know it? As #sci4hels were discussing this issue, what came up over and over was that you have to use common sense. You have to walk a thin line between what you know, what you know you can learn and how you present yourself and your abilities to your employers. If you claim to know something, and you fall flat on your face and don’t deliver the goods, you could do some real damage to your career. Not just because you’ll make your boss angry, not just because you might lose your job, not just because it might be embarrassing; but also because when you fail to deliver what started as a stretched bit of truth unraveled into a shameless lie. Getting caught in a lie in this business is a nail in your career’s coffin.
 
Sure, telling a lie about your ability isn’t the same as telling a lie in a story. I’m not saying that getting caught lying to an employer about what you can do is going to send your career to Lehrer type depths, but it isn’t going to help you get hired anywhere else. You run the risk of ending up labeled as someone who can’t deliver. Getting paid jobs as a science writer is hard enough, getting them once a pissed off editor tells all their connections not to hire you because you aren’t going to produce the work you say you will is going to be impossible.
 
This is a business about connections, if you start burning bridges so early in your career, you can really back yourself into a corner. It also speaks to character, doesn’t it? If you’ll lie about your abilities, what else will you lie about? How is anyone supposed to know where your professional ethics fall when you establish yourself as someone for whom a lie isn’t a lie it’s really more of a gray area.
 
So should we be telling young journalists that it’s okay to claim to be a master of science communication so long as you don’t fall flat on your face? It’s okay to lie, as long as you don’t fail and get caught. Is that really the lesson here? I have zero faith in advising journalism students to use common sense. Zero. If common sense were a clear boundary we wouldn’t still be spending entire class periods discussing what is Facebook appropriate (yes, even that cute picture of you playing beer pong with your Grandma probably doesn’t convey that you are serious about your career) and I’ve sat through those classes so I know very well what kind of questions students are asking. Use common sense doesn’t satisfy.
It's raining code, and apparently we're in the Matrix. Via Shutterstock

It’s raining code, and apparently we’re in the Matrix. Via Shutterstock

So then what are you supposed to do? The only answer that doesn’t present an ethical dilemma is to just learn code and then you’ll know you know it and you won’t be in a position where stretching the truth even comes up. Even someone with my stance has to agree that code is a nice skill to be packing in your arsenal. But this goes further than code. It could apply to any kind of program or web application; you can’t be an expert in everything. There are definitely going to be jobs that you might want where you don’t know the technology that is being used. It comes down to a personal risk vs. benefits assessment.

There is a lot to lose if you get caught claiming you can do things and not rising to the challenge – your reputation and your future prospects to name a few. There is also a lot to gain by forcing yourself to rise to the challenge to learn new things, get the job and stay competitive in this field. Maybe what new and young science journalists need is the kick in the rear that promising to deliver upon a skill brings. Maybe if I put myself in that situation I’d find that code isn’t nearly as bad as the Pythagorean theorem, and a lot of doors for future job prospects would get opened. Maybe I would torch my promising young career in a blaze of gray area glory.
 
Common sense is itself a gray area. If we are going to advise journalism students of anything, I’d say informed decision making is probably the way to go. You should be aware of the risks you take when you climb out on a limb with no safety net, but that doesn’t mean you shouldn’t still climb. It has to be a personal case by case call, which really doesn’t help much. Hopefully though, if you think through the risks and the benefits of how you can present your skills, you’ll come to a decision that is the right one for you and your career. So proceed with caution. 

The Question of Code

#sci4hels, Good Writing, Jobs, Science writing, State of Journalism, The Internet, Twitter,

Earlier this week Bora Zivkovic (@boraz) blogs editor at Scientific American tossed out the following links on twitter, and asked for thoughts. Both links were to articles from the Nieman Journalism Lab, the first Want to produce hirable grads, journalism schools? Teach them to code and the second News orgs want journalists who are great a a few things, rather than good at many present two different ways of thinking about the skills journalists need to have. The links started a conversation on twitter (excerpted below) between Bora, Rose Eveleth (@roseveleth) Kathleen Raven (@sci2mrow) Lena Groeger (@lenagroeger) and myself (@erinpodolak) I felt like there was more to say on the topic, so I decided to take it to the blog so that I could respond to everyone’s points without the confines of twitter brevity.

I definitely agree with this point from Rose, there are so many different skills you use as a journalist but a lot of what you need to know will vary based on your personal style and interests, what platform you write for, and what topics you are covering. I’ve found that I learned a lot more from going out and actually chasing down stories than I did sitting in classrooms. Of course, the guidance of journalism school makes learning by trial and error much less perilous than it can otherwise be, so classroom lessons have value too.
I moaned an awful lot about how scary being turned loose into the unemployed masses at the end of grad school seemed. Journalism has adapted to changes in viewership, platform and the poor economy, and so too must journalists or we run the risk of ceasing to be relevant. Making yourself as employable as possible is a good thing, but only if you are going after jobs where you can really contribute. You’ll only be able to contribute if either you know what you are doing or you have the desire and the drive to learn what to do. This thought brings me to the next point I made, not all the skills journalists use will appeal to all journalists. As a profession we can do a lot of different things, but that doesn’t mean that everyone wants to do everything.
If you are looking for a job, you have to be honest with yourself and your resume. I think for young journalists there is a temptation to trumpet skills that we only sorta, kinda, maybe have from that two hour seminar we sat through that one time. You can fit what I know about code on the head of a pin, and I’ve sat through basic training courses multiple times. My resume says nothing about being able to code, because I honestly don’t know how. It is always better to be honest about what you know. If you aren’t an expert in something, don’t claim to be. All you’ll do is disappoint possible employers. I think you can go a lot farther being honest about where you are with your skills, if you don’t know code but would like to then say so. If you’ve edited a video once or twice and would like to continue developing those skills then say so. Just don’t make yourself into an expert in something when you aren’t.
I recently graduated from the professional track Master’s program at the University of Wisconsin-Madison, a program that with only three core courses is left purposely open for students to do their own exploring. So what exploring did I do? I chose to spend my time taking science classes (mostly zoology) learning more about narrative writing and structure, and getting a better handle on social media, personal branding and marketing myself online. All good things to learn while at school, but I didn’t learn code. I honestly have zero interest in code, it isn’t something I’ve ever wanted to do, I don’t have the patience for it and I feel like my brain just doesn’t absorb even the basic information about code whenever it is presented to me. But that doesn’t make me an inept science writer. Kathleen Raven  joined the conversation, and brought up the following reason why not knowing code can still be okay.
Part of the reason I think I haven’t been particularly motivated to learn code is because I haven’t needed it. I was able to set up this blog and my website (www.erinpodolak.com) on WordPress using basic templates that suited my needs. I’m on Twitter, Facebook, LinkedIn and G+ but none of these online activities involve needing to write my own code. To do what I want to online I haven’t run into the need to write code. Kathleen then made another point about a science journalism skill, the ability to do math, which can be overlooked but is important to a writer’s skill set.
Being able to do the math to fact check research reports and call bullshit when necessary is an important part of the reporting that science journalists do for their stories. If you know code but can’t do math, you have a critical weakness in your skill set. In my opinion the same goes for being able to structure stories successfully, and handle difficult interviews well. If you don’t have the basics, then the extras like code are just floating out there on your resume with no foundation. Being really good at the basics, and then selectively adding skills based on what you find that you need to know, and what you find you would like to know seems like a solid way to go about building your skill set. I think this gets us to the last points that Rose made:
You need to do something that you enjoy. If you don’t enjoy code then in my opinion you shouldn’t feel like it is an essential skill to have. You might want to be the kind of journalist that can do it all, kudos to you for that. But, I don’t think there is anything wrong with wanting to have a few select skills and being really good at them. If you are honest with yourself and honest with employers I think you can definitely learn an array of skills that suit you and your job. We have options, and that is a great thing. Happy times, indeed.
Note: This is only a brief excerpt from the first few days of this conversation. Much more was said, including more back and forth between Lena, Rose and myself about skills and how to present yourself to employers and from Bora, Lena, Rose and Dan Fagin (@danfagin) about the structure of jschool programs and the balance needed to meet students needs. Still plenty more to say about these topics!
This conversation took place before we started the hashtag #sci4hels to mark all of the tweets. Be sure to monitor the hashtag in the future to see more of the on going discussion between Kathleen, Lena, Rose, Bora, myself and others!

New Job: The Dana-Farber Cancer Institute

Cancer, Dana-Farber Cancer Institute, My Personal Life, Science writing

After an incredibly crazy month of traveling, interviewing, and moving I have officially started my new full time job at the Dana-Farber Cancer Institute in Boston. I announced on Twitter a few weeks ago that I accepted a position with DFCI as a science writer for donor relations, but I realized I never really gave my blog readers any background on what I’ll be doing. After all my whining and pontificating about growing up and joining the work force, it wouldn’t be right to not explain what my new job is all about.

DFCI's new Yawkey Center via HelloBoston

DFCI’s new Yawkey Center via HelloBoston

As a science writer for donor relations my role is to research, gather information, and interview PI’s about research projects (mostly pre-clinical and clinical) on specific beats that I’ve been assigned. The beats are all specific subdivisions regarding research at DFCI, it could be a specific group of cancers like women’s cancers,  a particular research group or institute or a particular program or approach to looking for treatments. DFCI is one of the oldest and most accomplished cancer research institutes in the United States with a serious commitment to both research and patient care.

Once I’m up to speed about what has been going on with a particular beat I write up a narrative report about all of the cool things they have accomplished in the last year. That report is given to donors to showcase the work that DFCI researchers are able to accomplish with the funding that the donors give to the institute. I’m just starting to get into my first project, but I’m really excited. I’m going to get to interview amazing researchers, and get to learn more about really interesting approaches to finding treatments for cancer and related diseases. DFCI is using the most cutting edge technology and processes available to come up with new incredible ways to take down cancer cells, and I get to spend my days finding out all about it.
So, that is my new job in a nutshell. It required a move from New Jersey to Boston which has been an incredible, though tiring experience. For those who are interested DFCI has a fascinating (at least I think it is fascinating) history making breakthroughs in the treatment of cancer. DFCI was founded in 1947, as the Children’s Cancer Research Foundation, by Dr. Sidney Farber who was looking for a way to treat childhood leukemia. In the late 40’s leukemia was an automatic death sentence. Farber was the first in the world to achieve temporary remission of acute lymphotrophic leukemia (the most common form) using drugs (and later combinations of drugs) as treatment.
The foundation expanded to include adults in 1969 and was renamed the Sidney Farber Cancer Center in 1979 in honor of its founder. The name was changed again in 1983 to the Dana-Farber Cancer Institute to reflect the long term support of the Charles A. Dana Foundation. I’m going to guess everyone is familiar with the term chemotherapy, yes? Chemotherapy was developed at DFCI. There have been many other breakthroughs achieved at DFCI over the years, I suggest taking a look at the milestones to get a better idea.
Another interesting bit of DFCI is the formation of the Jimmy Fund and the organization’s relationship with the Boston Red Sox. DFCI was really one of the first cancer research organizations to successfully use public fundraising and awareness campaigns. A radio program in 1948 featuring “Jimmy” a childhood leukemia patient being visited by members of the Boston Braves baseball team prompted a huge influx of donations and the construction of the Jimmy Fund building on what is now DFCI’s main campus in Boston’s Longwood Medical Area. In 1953 the Boston Red Sox named the Jimmy Fund their official charity after the Braves left the city, which is a relationship that continues nearly 60 years later.
That is just some really basic information about my new job and DFCI in general. I really suggest taking a look at the DFCI website and the Jimmy Fund website if you are interested in learning more about the institute. I’m proud and honored to be working for such a great organization, and I can’t wait to see what comes next. Also watch this video, and feel the awesome.
Note: By NO means am I an authority on cancer research or treatments of any kind. I am NOT a medical doctor, and am not qualified to answer any medical questions you may have. If you would like to talk to someone at DFCI, you can call the institute at 866-408-3324.