Can Programmers, Journalists Get Along in One Newsroom?

One of the explanations for the emergence of the programmer/journalist is the move of news organizations from print (or radio or TV) to the web. While some newspapers have gone online-only, and many are still trying to move to a \"web-first\" mindset, there are still newsrooms that view the web as a secondary medium.\n\nI remember when every step forward at my college paper, the Independent Florida Alligator, was a hair-pulling, tooth-and-nail fight. It wasn't that the other editors didn't think the website was important. The problem was one of culture. I had been web-minded from the beginning of my journalism education, while most students remained entrenched in the print structure.\n\nSo how do you merge the culture of the programming environment with the culture of the newsroom?\n\nh2. Merging Two Cultures\n\n\n\nThe premise of the \"Knight Foundation\":http://www.knightfoundation.org/'s journalism scholarship for programmers is that \"there's no reason why a programmer can't do journalism,\" said Rich Gordon, director of digital innovation at \"Northwestern's Medill School of Journalism\":http://www.medill.northwestern.edu/. \"They just need an understanding of the mission and culture of journalism and journalists.\"\n\nGordon thinks that many of the perceived differences between a journalist and a programmer are false.\n\n\"Journalists and programmers are more alike than unlike,\" Gordon said. \"I think that people who wind up in programming are closer to introverted than extroverted, but this is true of many journos as well. Both groups, when hanging out with other people with whom they share interests, will lapse into jargon. It's worth pointing out that I've known some amazing journos who could bury their head in a major investigative project and do incredible research and reporting and be perceived as anti-social.\"\n\nAron Pilhofer, editor of interactive newsroom technologies at the New York Times, has assembled a team of mostly programmers to do journalism. He says the challenge is to bring programmers into the newsroom environment.\n\n\n\n\"It's not a normal corporate-y type of environment,\" Pilhofer said. \"It's very loosey-goosey, collaborative, hectic, disorganized. It takes time to get used to that environment, and not everyone is comfortable in that environment. Being comfortable working in a more agile, flexible environment is a matter of personality.\"\n\nThe newsroom lacks the structured corporate environment most programmers experience. There is no defined workflow, no requirements documents, and priorities can shift at a moment's notice.\n\nBut, Pilhofer said, \"It's been a rollicking success on our end. It's less of an issue than I thought it'd be. In two years, I have not run out of people who would fit into the environment.\"\n\n[Editor's Note: Pilhofer and Gordon both have received Knight News Challenge grants, and blog on MediaShift sister site, \"Idea Lab\":http://www.pbs.org/idealab. MediaShift also received a grant from the Knight Foundation.]\n\nh2. Need For Improved Communication\n\nMatthew Waite, news technologist at the St. Petersburg Times, weighed in on how programmers and journalists communicate, and how that communication can be improved. He said ill-will between journalists and programmers arises from miscommunication.\n\n\"I've seen a lot of cases where some piece of code did exactly what the requirements document specified, but it didn't do what anyone wanted,\" Waite said.\n\nThis problem comes from a common feature of project development in the programming culture -- the requirements document. This tells the programmer exactly what is needed. A programmer without media experience will do just what they've been trained to do -- build a project to meet these specifications.\n\n\n\nHowever, the programmer/journalist often knows the difference between what is needed and what's in the requirements document. Waite used his high school sports application, \"Home Team\":http://hometeam.tampabay.com/, as an example of how programmers can understand what a journalist wants.\n\n\"You need to go do what you're being asked to build,\" he said. \"Spend a night on the sports copy desk taking high school football scores and you'll get an idea of what a football score taking app should do, no matter what the editor is telling you.\"\n\nSimilarly, journalists would do well to sit with a programmer and watch their ideas get turned into an app.\n\n\"The journalist/programmer has the advantage of having this cross-domain specific knowledge already,\" Waite said. \"They've written the murder story before so they have a much better idea of what a murder database app should do.\"\n\nMegan Taylor is a web journalist whose work focuses on combining traditional and computer-assisted information-gathering with multimedia production to create news packages online. Megan tells stories in English, HTML/CSS/, ActionScript, PHP, photos, video and audio, and blogs at \"her personal site\":http://www.megantaylor.org/.