Hackerspaces in Public Libraries

I was interviewed as part of an NPR Weekend Edition story by Jon Kalish called libraries making room for hackerspaces (Saturday Dec 10).


A hackerspace is people owning something together, sharing resources, sharing knowledge, valuing curiosity and creativity, engaging in productive inquiry. If one can see beyond the specific tools populating the traditional physical space, libraries and hackerspaces look a lot alike. The resemblance is more than a resemblance; a hackerspace is really just a library by another name.

There’s nothing scary or criminal about the term hacker. A hacker is a person who enjoys exploring the details of programmable systems and stretching their capabilities, as opposed to most users, who prefer to learn only the minimum necessary. Using the science/engineering concept of a black box, where only inputs and outputs are visible, not the internal workings, the hacker wants to open the box. The hacker further insists that if you can’t open it, you don’t own it. So in the way that libraries have always existed to understand the world better, to explore how stuff works, to illuminate the inner components of any area of interest, they have always been hackerspaces. Furthermore, as institutions owned by the public, libraries should not be black boxes. We should all be able to look inside and collectively tinker with the inner workings of these places.

The message of the library is that we can learn, we can become aware. We are not forced to remain in the dark. And while becoming aware is an important achievement, I think the public space of a library affords much more; I think it can provide options for activity that can enhance human agency.

I first learned of 3d printing around 2005 from Thomas Gokey, a then grad student at the School of the Art Institute of Chicago who showed me a house being printed in cement. I spent some of my time in my library grad program working on what personal fabrication and easily programmed microcontrollers like Arduino will mean for us, how the easy conversion between digital and physical ends the zero-sum economy and ushers in a system full of non-rival goods–we can think of it as turning the whole world into a giant public library. I was studying this technology in light of Hardt & Negri’s Empire and Multitude (Commonwealth wasn’t out yet even though that would have been the most relevant book in the trilogy for my purposes), Yochai Benkler’s The Wealth of Networks, and hunting for recent work on post-scarcity economics.

I never published a paper on it, but when Dave Lankes asked me to teach in SU’s library science program (and half-jokingly insisted I wasn’t allowed to say no), we agreed the class would make a good outlet for passing along some of the ideas that I’d worked on but not had a chance to implement. Students and I would get to work on them together, and this was attractive to me. When Thomas Gokey and I presented Fab Labs/maker-/hackerspaces and took a field trip to a tech shop at SU, Lauren Britton-Smedley was one of the students who really got it, and she was ambitious enough to suggest a home for it in the Fayetteville Free Library. This is exactly the kind of thing we were hoping would come out of our class. Every instructor dreams of having a student like Lauren in class, who trusts what she’s learning enough to risk acting on it. I think of projects like the LibraryFarm and the FFL Fab Lab as publications, only superior to traditional publications. They represent research and production and can function as rhetorical devices that contribute important new ideas and conversation to the field of public librarianship, but they’re not limited by text. They exist in the world as experiences and interventions; non book-like objects that can advance our understanding.

The main text we used for our class was Douglas Rushkoff’s Program or Be Programmed. Rushkoff’s thesis is that in the emerging highly programmed world if you are not creating software, you are the software. If you’re on facebook, you think you’re using Facebook but you are being used by Facebook: you are part of the program that has been written to generate massive amounts of data on consumers. Only once you understand how Facebook works, when you understand how its handling your bits, can you interpret what it’s really for, and make a decision about whether and how you might use it. We’ve got to learn to see the code running our society, not just the inputs and the outputs. That’s what an informed citizenry will mean in the 21st century.

About The Author

Meg

Other posts by

Author his web site

2 Comments Add Yours ↓

The upper is the most recent comment

  1. Christopher Diehl #
    1

    Meg: Fascinating stuff! I am an architect in Cleveland, Ohio, leading a team in the design of a new county branch library. We have spent a great deal of time planning for an evolution of “library” that promises only to exceletate.

    The notion of “Hakerspaces” fits well into that discussion and, perhaps because it hits so close to home to how we are trained in architecture school, I hadn’t seen that one coming. Of course, the library could extend its mission of information and mind expansion infrastructure to incorporate the physical. Architects can imagine extraordinary things with software these days but they must, at day’s end, manifest themselves within the built environment. Regardless of digital wizardry, physical models remain the most successful way to communicate proposals and to proto-test notions empirically. Ultimately, the building must get built and without the aid of Photoshop filters or animation techniques.

    So, to create a small workshop/laboratory within a libary program, does sound fantastic yet doable. The Fort Wayne, Indiana example in the NPR piece was notable in that it was essentially outsourced to a third party. The biggest challenge that I see is not in creating the architectural infrastructure to support this, but in the required staffing infrastructure and financial start-up costs. What have you found in this regard?

    Thanks again and best regards,

    Christopher

    • Meg #
      2

      So Christopher, are you working with Sari Feldman on this new library? I’m jealous: designing a new library and working with Sari are 2 things I’d kill to do.

      The workshop/laboratory aspects of a library do not have to be high tech. At my library, we’ve plowed the land the library is on and we collectively farm it, which constitutes a low-tech hackerspace. People teach each other, experiment, share tools/strategies/labor/food. We wish the library’s roof had been designed to collect rain water. Nevermind a cafe, we wish it had a kitchen. The LibraryFarm costs almost nothing and requires almost no staff support. The LibraryFarmers have the latitude to manage themselves and their space. The rules are that they can’t exclude anyone.

      We have paper crafting equipment–die-cuts and a cricut machine and reams of donated papers. Again, teeny tiny start-up costs, very little staff involvement.

      We have a large knitting group that camps out at the library once a week, giving aid to knitters who are stuck, lending gear, patterns, technical knowledge to each other. Architecturally, I wish the space of the library accommodated them better. They pull together 2 dozen chairs in an area that partially blocks access to certain collections, plus crowds out a couple computer stations (they don’t want to be shut off in a separate room, they want to be out amid the public, part of the activity of the library proper).

      These are all workshops/laboratories. All kinds of hackerspaces. It’s about giving ownership/control of the commons to the people. Bre Pettis (Makerbot Industries) reassured a group of us meeting at ContactCon earlier this year that money is not an essential ingredient for a successful hackerspace. People are far more important. People who identify with a space or project–not money–will be capable of sustaining said space or project.

      Sounds risky, I know. Sounds too if-you-build-it-they-will-come. The challenge is to build policies and procedures aligned with a physical atmosphere that inspires wonder and promotes exploration and cooperation. The hardware has to fit the software (and the architect doesn’t build the software (which is why you’re lucky if you’re working with Sari)). This represents a significant shift in library work, and it’s indeed a serious challenge. Staff attitude matters more than staff expertise, but cultivating an ethos that relinquishes control can be harder than cultivating expertise.



Your Comment