So Patrick and I have been conspiring a bit to have a sort of hackathon at THATCamp, and you’ll see that there’s time and space reserved for it on the schedule — basically all weekend in CHNM itself on the fourth floor of Research Hall, in the same space the CHNM developers use every day — long tables and lots and lots of whiteboards — plus the lounge area — sofas, soft chairs, and coffee tables. Everyone’s also welcome to use this as a co-working space to code whatever they like, whether for the hackathon or no (and there’s a WII with MarioKart, which you’re also welcome to use).

On Friday at 9:30am, Patrick will introduce one or more datasets for the hackathon, but you can also just work on whatever you like. We’ll be having a lightning round demo (3 minutes apiece) on Sunday from 12:00-12:30, and everyone who participates in the demo will get a small prize for participating. There won’t be any official judging; any competition among the participants will be strictly subtextual. Even beginner folks who want to use this as a practice session to mess around with Omeka or ViewShare or Weka are welcome to participate.

You are all encouraged to build things either individually or in groups, for example by having a coder and a designer team up to put together an awesome new visualization on some data.

To recap the chief features of the Hackathon:


CHNM, 4th floor of Research Hall.

Intro at 9:30am by Patrick, coding all weekend, demos from 12:00-12:30 on Sunday.

We’ll suggest a couple of datasets for you to work with, but you can also build something all on your own.

About Amanda French

(Please ask any THATCamp questions on the THATCamp forums at http://thatcamp.org/forums -- I'm no longer THATCamp Coordinator.) I am now a member of the THATCamp Council, and I am the former THATCamp Coordinator and Research Assistant Professor at the Roy Rosenzweig Center for History and New Media at George Mason University, in which capacity I provided support for THATCamp organizers and participants, maintained http://thatcamp.org, traveled to some (not all!) THATCamps, and directed large-scale projects such as the Proceedings of THATCamp. Before that, I worked with the NYU Archives and Public History program on an NHPRC-funded project to create a model digital curriculum for historian-archivists. I held the Council on Library and Information Resources Postdoctoral Fellowship at NCSU Libraries from 2004 to 2006, and afterward taught graduate and undergraduate courses at NCSU in Victorian literature and poetry as well as in the digital humanities and in advanced academic research methods. At the University of Virginia, while earning my doctorate in English, I encoded texts in first SGML and then XML for the Rossetti Archive and the Electronic Text Center. My 2004 dissertation was a history of the villanelle, the poetic form of Dylan Thomas' "Do not go gentle into that good night" and Elizabeth Bishop's "One Art."

8 thoughts on “Hackathon

  1. Actually, the intro to hackathon won’t take long, and hackathoners might also want to go to the first workshops.

    Does anyone want to hear about that hackathon, datasets, and see the space AND want to attend the first workshop sessions? If so, I’ll try to figure something out to accommodate!

  2. I would definitely like to participate. I’m currently set to attend the first workshop sessions but could head out a little early if necessary.

  3. The Hackathon intro is going to be very brief indeed, so we went ahead and moved it to 9:15, before the workshops, so that people will have time to hear how it works before going to the workshops. See the revised schedule. To be frank, really Patrick is just going to explain some things about the space (“Here it is! CHNM!”) and recap this blog post, plus answer any other questions.

  4. I am so very interested in this, and I’m not planning on attending any Friday workshops.
    There’s a chance I might need to miss parts of the weekend, though; does the lab have a setup that would be good to share the hackathon via Google Hangout (something Dave suggested on Twitter)?

  5. I don’t see why not — it’s not really a lab, just a big open space, so the only issues might be with sound, but in my experience Hangout is pretty good about eliminating echo. Really it’ll be just a bunch of people hanging out coding — people can work individually or in pairs or groups.

  6. really looking forward to as most of the thatcamps I’ve gone to in the past haven’t had this particular element.

Comments are closed.