What Government Can and Should Learn From Hacker Culture

It's not enough to just bring geeks into government—bureaucracies have to learn to encourage collaboration and flatten the hierarchy, too.
The Bazaar of Athens, Edward Dodwell

South by Southwest isn’t generally associated with the federal government. But this year, between panels on “10 Things Your Band Can Do To Not Get Sued” and “Austin Breakfast Tacos: The food, people & history,” the festival will host “It’s Not About Tech: Hack the Bureaucracy.” The pitch: “Bringing geeks into government won’t make a difference if they can’t crack the code on bureaucracies.” Steering the panel is veteran government code-cracker Richard Boly, former head of the State Department’s Office of eDiplomacy.*

That the State Department embraces technology should not come as news. The department’s “21st Century Statecraft” initiatives have been well covered in the press, and officials from the secretary down to the interns use social media. But the SXSW panel focuses on a far thornier issue than getting ambassadors on Twitter: how to foster a culture of innovation and openness in a bureaucracy built to resist change.

The term “bureaucracy” has few positive connotations. It’s been called the “death of all sound work,” (Einstein), the “giant power wielded by pygmies” (Balzac), the “slime” left behind when revolutions fade (Kafka), and a “symbol of hell” (C.S. Lewis). Though it isn’t America’s only bureaucracy, the federal government is probably its most infamous one. The Pew Research Center for the People and the Press shows only 28 percent of Americans viewed the federal government favorably in 2012, its lowest rating since the poll began in 1997. The study didn’t delve into why, but perhaps part of the answer is the perception of federal agencies as bloated, ineffective bureaucracies that stifle creativity.  

But there’s hope government can change this. The software industry can show us how. A little more than 20 years ago, Linux triggered a paradigm shift in programming, from hierarchy and restriction to collaboration and openness. It gave rise to practices that now seem commonplace, like cloud computing and crowdsourcing. But most importantly, it transformed the culture of programming. From a field primarily focused on producing products, tech development became what IT pioneer Tim O’Reilly called a whole new field of "scientific and economic inquiry." If that formerly stratified world could transform how it did business, maybe government can as well.

Before Linux, the software industry looked very different. As tech advocate Eric Raymond wrote in The Cathedral and the Bazaar, proprietary software firms used to resemble the grand churches of old; those in charge cloistered from the common folk, their discussions secret, decision-making a top-down, fixed-route operation. With open source, development came to resemble a "great babbling bazaar of differing agendas and approaches," with many contributors working collaboratively. In the bazaar model, what matters is not rank but who finds the answer. The benefits of the approach are summed up in the aphorism, "With enough eyeballs, all bugs are shallow." In other words, the more eyes on a problem, the better the odds are of finding the root cause.

At first, many companies rejected open source. As recently as 2001, Microsoft CEO Steve Ballmer called Linux a "cancer" on the programming industry. But in two short decades, the model went mainstream, with corporations and government agencies, including the White House, now operating on open-source platforms. Eleven years after the "cancer" comment, Ballmer publicly embraced Linux. IBM declared last year that open source models "stand(s) ahead of their closed source counterparts" in just about every significant way.

Can the open-source model work for federal government? Not in every way—for security purposes, the government’s inner workings will never be completely open to the public. Even in the inner workings of government, fears of triggering the next Wikileaks or Snowden scandal may scare officials away from being more open with one another. While not every area of government can be more open, there are a few areas ripe for change.

Perhaps the most glaring need for an open-source approach is in information sharing. Today, among and within several federal agencies, a culture of reflexive and unnecessary information withholding prevails. This knee-jerk secrecy can backfire with fatal consequences, as seen in the 1998 embassy bombings in Africa, the 9/11 attacks, and the Boston Marathon bombings. What’s most troubling is that decades after the dangers of information-sharing were identified, the problem persists.

Presented by

Alexis Wichowski is an analyst at the Department of State and an adjunct assistant professor at Columbia University’s School of International and Public Affairs. 

How to Cook Spaghetti Squash (and Why)

Cooking for yourself is one of the surest ways to eat well. Bestselling author Mark Bittman teaches James Hamblin the recipe that everyone is Googling.

Join the Discussion

After you comment, click Post. If you’re not already logged in you will be asked to log in or register.

blog comments powered by Disqus


How to Cook Spaghetti Squash (and Why)

Cooking for yourself is one of the surest ways to eat well.


Before Tinder, a Tree

Looking for your soulmate? Write a letter to the "Bridegroom's Oak" in Germany.


The Health Benefits of Going Outside

People spend too much time indoors. One solution: ecotherapy.


Where High Tech Meets the 1950s

Why did Green Bank, West Virginia, ban wireless signals? For science.


Yes, Quidditch Is Real

How J.K. Rowling's magical sport spread from Hogwarts to college campuses


Would You Live in a Treehouse?

A treehouse can be an ideal office space, vacation rental, and way of reconnecting with your youth.

More in Politics

Just In