What j-schools can learn from music conservatories: CompJ

Was Computation + Journalism an academic conference or an industry conference?

It's hard to say, especially when nearly every panel through its two days featured a working journalist and an educator, and an equally diverse audience pressed questions from many ends of the field.

Unsurprisingly, the debates that came to the fore early and often centered around that intersection between educators and practicing journalists. As a student in a journalism school, I paid special attention to the discussion around what students should be learning in journalism school to prepare them for becoming a practicing journalist.

During his presentation, Storytelling with Data Visualization, Alberto Cairo finished his opening statement by asking, "Should all journalists learn to code?"

While he didn't answer the question explicitly, I answer yes — with a caveat.

Do all journalists need to learn how to create and maintain a dynamic, data-driven application on their own self-hosted server? Probably not.

Do all journalists need to know how to get their content on the web and present it effectively? Absolutely. HTML and CSS skills are essential to succeeding at any publication with a web product — that is, any publication with a pulse.

But many programmers will say "HTML is not coding; it's markup." True. Which is why we need to go further and teach the fundamentals of programming. It matters not if you teach Python or JavaScript or R, (indeed, students could choose based on their interests) because those tools will almost certainly go away within any young journalist's lifetime.

What's more important, and Cairo agreed later in the panel, is the notion of computational literacy. Journalists need to know how to use the tools in front of them to make their stories better. They need to know what is possible and what is not. Even if they do not explore programming at a deeper level, they need to know how to work with developers in their newsrooms.

At many different levels and throughout many panels, Computation + Journalism dealt with how to integrate computational literacy into our journalism schools. Philip Meyer opened the conference by stating that journalism is in a "state of chaos." Something new is going to come out of the chaos, and we have to build it. Why not start at the journalism school level? Meyer wondered if journalism schools couldn't take more of a role in defining what journalism is. If journalism is going to have a successful future, computational literacy has to be a part of the equation (in addition to storytelling, critical thinking, and other more traditional journalistic skills), and it has to come at the educational level.

Related to computational literacy is the notion that journalists must pivot from tool users to toolmakers. Meyer, Jer Thorp, Nicholas Lemann, and others harped on this point throughout the two days. The toolmakers in our field — Mike Bostock, Jeremy Ashenkas, and anyone who has ever open-sourced a project — have been indispensable, but we must not forget how to use the tools of others for our own bidding. The apps we create are built on the shoulders of the best open-source technology, and it takes a skilled user — indeed, a computationally literate user — to know how to piece everything together. Smart usage is an important component of learning how to work in web journalism.

So what model can journalism schools create to properly educate its students in a world of computational journalism? The model may already exist.

I spent a year studying music while at Northwestern, and I find that the new needs of a journalism school parallel that of a traditional music school or conservatory. At a typical music school, you will have (at least) three interdependent fields of study: performance, composition, and education. Performers require a special level of craft on their chosen instrument, perfecting tone quality, technical dexterity, musicality, and all the other facets that make a great performing musician. Composers learn how to create music that performers play, yet what makes classical music so interesting is the way different performers interpret compositions. Educators bridge the gap between performers and composers. In a way, they are performers themselves as conductors, but more importantly, they learn skills that help them rehearse a group of performers and teach them how to correctly interpret the composer's music within the context of the performing ensemble.

The analogues to journalism are easy to draw in the context of the tool using vs. tool making debate. Performers are our writers, reporters, photographers and videographers. They fall here because they are the tool users. Though certainly they carry elements of composers through their creative process, this is the same as how musicians “make music.” In this model, they perform journalism rather than create it through an already composed set of journalistic tools. The composers are our toolmakers, our developers that create the applications and libraries that modern journalism is founded upon. In the journalism world, the educators are our editors and project managers. They organize the groups of performers and define the voice of the publication. They choose the tools with which journalism will be performed. Like the conductor connects the performer to the composer and the individual to the ensemble, they connect the reporter to the developer and the story to the publication.

Certainly, this is not a perfect model, and I am not advocating for "Journalism Performance" majors. But the model helps divide the different needs this new world of computational journalism needs. We need both skilled users and creators as well as strong leaders to help keep us all together and lead our publications.

The questions raised at Computation + Journalism have already begun to define this divide in skill set. Are we all to be programmers and toolmakers, or simply understanding of the Internet's capabilities and able to perform them?

Certainly, we must all understand how computational journalism affects our craft. But the path to the composer will not interest every journalist, and it should not be for every journalist. Instead, just as every music student learns introductory music theory, but only some become composers, every journalist should learn introductory programming, and only some will become developers.

About the author

Tyler Fisher

Undergraduate Fellow

Latest Posts

  • Introducing StorylineJS

    Today we're excited to release a new tool for storytellers.

    StorylineJS makes it easy to tell the story behind a dataset, without the need for programming or data visualization expertise. Just upload your data to Google Sheets, add two columns, and fill in the story on the rows you want to highlight. Set a few configuration options and you have an annotated chart, ready to embed on your website. (And did we mention, it looks great on phones?) As with all of our tools, simplicity...

    Continue Reading

  • Join us in October: NU hosts the Computation + Journalism 2017 symposium

    An exciting lineup of researchers, technologists and journalists will convene in October for Computation + Journalism Symposium 2017 at Northwestern University. Register now and book your hotel rooms for the event, which will take place on Friday, Oct. 13, and Saturday, Oct. 14 in Evanston, IL. Hotel room blocks near campus are filling up fast! Speakers will include: Ashwin Ram, who heads research and development for Amazon’s Alexa artificial intelligence (AI) agent, which powers the...

    Continue Reading

  • Bringing Historical Data to Census Reporter

    A Visualization and Research Review

    An Introduction Since Census Reporter’s launch in 2014, one of our most requested features has been the option to see historic census data. Journalists of all backgrounds have asked for a simplified way to get the long-term values they need from Census Reporter, whether it’s through our data section or directly from individual profile pages. Over the past few months I’ve been working to make that a reality. With invaluable feedback from many of you,......

    Continue Reading

  • How We Brought A Chatbot To Life

    Best Practice Guide

    A chatbot creates a unique user experience with many benefits. It gives the audience an opportunity to ask questions and get to know more about your organization. It allows you to collect valuable information from the audience. It can increase interaction time on your site. Bot prototype In the spring of 2017, our Knight Lab team examined the conversational user interface of Public Good Software’s chatbot, which is a chat-widget embedded within media partner sites.......

    Continue Reading

  • Stitching 360° Video

    For the time-being, footage filmed on most 360° cameras cannot be directly edited and uploaded for viewing immediately after capture. Different cameras have different methods of outputting footage, but usually each camera lens corresponds to a separate video file. These video files must be combined using “video stitching” software on a computer or phone before the video becomes one connected, viewable video. Garmin and other companies have recently demonstrated interest in creating cameras that stitch......

    Continue Reading

  • Publishing your 360° content

    Publishing can be confusing for aspiring 360° video storytellers. The lack of public information on platform viewership makes it nearly impossible to know where you can best reach your intended viewers, or even how much time and effort to devote to the creation of VR content. Numbers are hard to come by, but were more available in the beginning of 2016. At the time, most viewers encountered 360° video on Facebook. In February 2016, Facebook......

    Continue Reading

Storytelling Tools

We build easy-to-use tools that can help you tell better stories.

View More