A student in the back row, two or three minutes into the part of the lecture I cared most about, raised her hand and asked, "If I want to be a real reporter, do I actually have to know any of this?" She wasn't being rude. She was asking me, plainly, whether the web was a serious place to do journalism or a side door that real writers could avoid.
That was Medill on February 22, 2002. Rich Gordon of Medill, Northwestern's journalism school, and Brian Dennis of computer science had invited me to discuss Cofax, the newspaper publishing system my team developed at Knight Ridder. Dennis was leading a course that brought journalism and computer science students together to study content management systems. I also joined an afternoon panel about journalists and technologists working together.1
I came in thinking I was there to teach them how newsrooms were changing. The student's question made me listen to what choosing that work meant to someone at the start of a career.
The question under the question
Her question was about status as much as HTML. In the newsrooms I knew, the prestigious byline ran in print. The web desk was often treated as a rebroadcast channel, with a smaller salary band. Students were paying attention to those incentives. Advising them to take the web seriously meant asking them to choose work that their first editor might value less.
I had been running web operations at Knight Ridder Digital and before that at Philly.com, so I had spent years watching this incentive gap play out inside newsrooms. I had not expected to watch a twenty-one-year-old work out the same calculation in front of me. It was a clearer view of the problem than another newsroom meeting would have given me.
I answered her honestly. Yes, the web is where your work will eventually live. No, I cannot promise that your professors or your first editor will treat that as equally prestigious. Those were the conditions in which she had to decide how to bet.
The joint course itself was a reason for optimism. Gordon and Dennis were giving students a way to cross boundaries that still divided many newsrooms. Professors could create that opportunity; a visiting practitioner could add an account of what happened when those ideas met deadlines, budgets and newsroom habits. Academic and newsroom incentives did not always reward the same choices. Students deserved to hear that tension discussed plainly.
The questions I could not answer neatly
I had expected the journalism students to ask about tools and the computer science students to ask about architecture. The questions came out the other way around.
The computer science students wanted to know how editorial decisions got made. Who decided what went on the homepage? How did a breaking-news situation ripple through a production system? Could the software reflect the judgment calls editors made a hundred times a day, or would those calls always sit outside the code?
Those were questions I was working on inside Knight Ridder, and I did not have tidy answers. Standing in front of a room of undergraduates and saying "we are still figuring this out" was uncomfortable. It also gave us something worth discussing together.
My prepared remarks covered content management systems, the difference between print and web production pipelines, and why a newspaper's web operation behaved less like a printing press and more like a small broadcast network. I had slides and examples. The students' questions reached beyond the machinery to the people making decisions with it.
Give students a decision they can change
Cofax was already in newspaper use, and we had made it available as open source. Before the visit, I had told Gordon and Dennis that I would welcome feedback or improvements from students. Afterward, I encouraged them to try it, including for their own sites. They could examine decisions made for a working newsroom and try an answer of their own.
For such a class, I would propose a student news site with sections for campus news and student finances. A report about a tuition increase could be useful in both. Ask a pair of students to find out how the publishing system assigns a story to a section. Does it allow the same story to appear in both places, or require the editor to choose one?
If it requires one, I would ask them to try allowing two section listings to lead to the same story. They would have to follow the choice from the editor's screen into the stored information and back out to the pages readers browse. Adding another box to the screen would not accomplish much if the software still stored only one section or displayed only the first selection.
The students should explain why the change helps a reader, too. If editors put every story in every section, the sections stop being useful guides. The class has to consider both what the software permits and how an editor would use that permission. Neither the number of checkboxes nor the fact that the program runs settles the editorial question.
I would not divide the work strictly by department. One student might be quicker to explain how readers look for news; another might trace how the program stores a selection. Both need to understand the change well enough to explain the part outside their usual work. A working example gives them something specific to point to when their explanations differ.
Newspaper software also has to work with existing material and with people publishing on deadline. I would ask the students to use a separate installation with sample stories, including an older story with only one section assigned. Their improvement should keep that ordinary case working. My responsibility would be to explain constraints they had not encountered, and to consider their questions without treating the existing system as the final answer.
A proposed change would still need examination before the people responsible for a newspaper decided whether to adopt it. I would want feedback that included the story the students were trying to publish, what the software made difficult, and what they tried instead. Even a proposal we did not adopt could give us a clearer question to answer. The class could keep working after the guest had left, and the guest could learn from what they found.
I had underestimated how much a guest lecturer could do by giving students confidence to choose an uncertain path. They were deciding whether to spend their twenties on this work. Describing a publishing system helped; showing that its unresolved problems were worth their attention helped more. I left Medill with questions I wanted to keep working on, and with a better understanding of why the students were asking them.
Looking back — September 2026
Later, at The New York Times and The Wall Street Journal, I carried a hiring rule that began in that classroom. When I interview someone early in a career, I pay attention to whether they have made the bet that student was asking about. Coding ability is one part of it. I also want to know whether they understand that the work will live on screens and that audiences will arrive through links, search and social feeds. Someone who treats the web as a secondary channel starts behind the work they have been hired to do.
I often find a journalism graduate who has understood that more useful on day one than a computer science graduate who has not. Credentials tell me something about preparation. The questions a candidate asks tell me how they see the work.
By the time some of those students were about ten years into their careers, a few had crossed my path again in newsrooms and at conferences. They had found their own ways through those changes, often faster than I had. What I had wanted to give them was confidence that the field they were choosing was alive, and that they could help shape it.
On subsequent campus visits, I spent less time on the slides and more time on the decision underneath the students' questions. It was a better use of the hour.
Footnotes
-
Eric B. Hanson, Journalists, Techies Make Connections, Medill School of Journalism, February 28, 2002. The report describes the afternoon panel and the joint journalism and computer science course. ↩