The Silent Code: Why Journalism’s Open-Source Culture Collapsed and How to Rebuild It

If you have spent any significant time in the technical trenches of a newsroom over the last two decades, you likely remember the "show your work" era. It was a time of infectious enthusiasm. Newsroom developers—often affectionately called "news nerds"—shared their code on GitHub with abandon, swapped debugging tips on social media, and published long-form blog posts that served as architectural blueprints for how to build interactive maps, scrape public data, or deploy web applications.

Back then, the spirit of openness was the industry’s lifeblood. It was a period defined by a collaborative ethos that suggested the biggest challenges in journalism could be solved collectively. But if you have felt a recent chill in the air, a vague sense that the community-driven innovation of the past has evaporated, you are not alone. You are witnessing the steady, silent decline of the open-source culture that once propelled online journalism into the modern age.

Data confirms the hunch: the movement has not just slowed; it has, by most metrics, collapsed.

The Quantitative Decline: A Shrinking Digital Footprint

The numbers are stark. An analysis of public project activity on GitHub—the primary repository for the world’s software development—reveals a grim trajectory for news organizations. In 2016, media outlets posted more than 2,000 public projects. By last year, that number had plummeted to fewer than 400. That is an 80% decline in less than a decade.

The retreat extends beyond code. The NICAR-L listserv, long considered a mandatory, daily diet for any data journalist worth their salt, has seen activity drop 89% from its peak. Where there was once a flood of peer-to-peer support, there is now a trickle of silence.

This collapse is not merely a byproduct of the broader recession in the media industry, though that is certainly a factor. A decade ago, outlets like BuzzFeed News, Mic, and FiveThirtyEight were prolific contributors to the open-source ecosystem. Their closures or pivots created a significant vacuum. Yet, the trend is not exclusive to struggling outlets. Even industry titans that once defined the "show your work" era have pulled back significantly. The New York Times, which for years set the standard for releasing open-source repositories, posted zero new public projects in 2024.

A Chronology of Innovation: The Rise and Fall

To understand the magnitude of this loss, we must look at what was built during the industry’s golden age of collaboration. In the early 2000s, newsrooms weren’t just covering the internet; they were actively building it.

In 2003, developers at the Lawrence Journal-World in Kansas created Django, a high-level Python web framework designed to handle the complex demands of a newspaper moving its content online. Django eventually grew to become one of the most popular web frameworks in the world, powering the foundation of platforms ranging from Instagram to the Washington Post.

Following this lead, institutions like NPR, The Guardian, and The New York Times developed custom content management systems and data visualization tools that pushed the boundaries of digital storytelling. ProPublica, meanwhile, set the gold standard for transparency, publishing detailed white papers alongside major investigations. These documents allowed peers to verify methodologies and learn from the quantitative rigor applied to investigative work.

This culture served as a beacon, drawing civic-minded technologists into journalism. It offered a rare opportunity: the ability to code for public good, solve societal problems, and contribute to a global library of knowledge.

The Drivers of Retreat: Why the Sharing Stopped

Through interviews with more than a dozen leaders from across the media landscape, three distinct patterns emerged to explain the industry’s inward turn.

1. The Economic Squeeze

The most intuitive driver is the harsh economic reality of modern media. When newsrooms face existential threats, resources for "extracurricular" activities like documenting and open-sourcing code are the first to be cut. As Dhrumil Mehta, a former FiveThirtyEight staffer who now teaches at Columbia and Harvard, noted, "The biggest barrier is just that [the organizations that shared] are not there anymore."

Moreover, the contraction has fostered a defensive posture. In a market where job security is increasingly rare, some developers feel that keeping their technical "secret sauce" locked away provides a measure of career protection.

2. Technological Maturity and the "Datawrapper" Effect

A more complex reason for the decline is the maturation of the software ecosystem. In the early 2000s, there were few off-the-shelf tools for newsrooms, forcing them to build from scratch. Today, many of those problems have been solved by commercial vendors.

"The decline might actually be a sign of success," argues Aron Pilhofer, who led teams at The New York Times and The Guardian. "We don’t need 18 different frameworks. Svelte exists. D3 exists. Datawrapper exists."

When commercial tools like Datawrapper offer polished, reliable solutions for data visualization, the incentive to build and maintain a custom, open-source equivalent diminishes. Furthermore, the rise of tech giants in the space—with frameworks like React and Angular—made it harder for news organizations to compete in the "tool-building" arena, leading many to adopt external solutions rather than creating their own.

3. The Inward Shift and Institutionalization

Perhaps most significantly, the culture of newsrooms has shifted. As technical teams became more integrated into core business operations, they were absorbed into the standard corporate hierarchy.

"You pushed further and further into the center of the newsroom and became more inward-facing," explains Paul Bradshaw, who runs the Online Journalism Blog. This professionalization brought with it corporate metrics: OKRs (Objectives and Key Results), sprint goals, and quarterly reviews. In this environment, open-sourcing code rarely contributes to a promotion or a quarterly bonus. If it isn’t rewarded by leadership, it effectively ceases to exist.

The Implications: Why We Need a Revival

The loss of this culture comes at a precarious time. We are currently at the precipice of an AI-driven technological revolution—the largest since the inception of the web. Without a collaborative spirit, newsrooms risk being siloed, tackling the same massive challenges (such as AI trust, audience loyalty, and business sustainability) in total isolation.

As one attendee at the News Product Alliance (NPA) summit in Chicago put it, "This is a time when we most should be sharing with each other."

A Path Forward: Rebuilding the Ecosystem

The decline of open-source journalism is not a permanent state of affairs. At the NPA summit, dozens of industry professionals gathered to map out a path for revival. The solutions proposed are not reliant on massive government grants or revolutionary business models; they require, instead, a shift in professional norms.

Recommendations for the Industry:

• Individual Agency: Developers can start by contributing to existing projects rather than starting new ones. Filing issues, improving documentation, or submitting a pull request to a colleague’s repo builds momentum. Furthermore, sharing "how I did this" project write-ups—like those published by The Pudding—provides value without the overhead of maintaining code libraries.
• Institutional Support: Newsrooms must treat open-source contributions as a core part of the job. This includes creating roles like "Open-Source Editor," whose primary responsibility is to package and release internal tools, and formally including contributions in performance reviews and promotion criteria.
• Industry-Wide Recognition: The creation of awards or public recognition programs for outstanding open-source contributions could help align individual efforts with career advancement. Additionally, conferences should prioritize space for "problem-sharing" hackathons—venues where teams can list the hurdles they are currently facing, even if a solution hasn’t been built yet.

The tools for collaboration still exist. The platforms remain. The talent is still in the newsrooms. What is missing is the collective recognition that by sharing our work, we make the entire industry more resilient, more innovative, and better equipped to serve the public. We must return to the habit of showing our work—not just because it’s the right thing to do, but because the future of digital journalism depends on it.