<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[CODEX HACK - Medium]]></title>
        <description><![CDATA[Thoughts from the Edge of Innovation around Publishing, Books, Libraries and All Things Literary. - Medium]]></description>
        <link>https://medium.com/codex-hack?source=rss----3a818604ad72---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>CODEX HACK - Medium</title>
            <link>https://medium.com/codex-hack?source=rss----3a818604ad72---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:24:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/codex-hack" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Photographic Journey through a Literary Hackathon]]></title>
            <link>https://medium.com/codex-hack/a-photographic-journey-through-a-literary-hackathon-7e091a3990b3?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e091a3990b3</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[literature]]></category>
            <dc:creator><![CDATA[Fyza Parviz]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 20:50:23 GMT</pubDate>
            <atom:updated>2018-02-25T04:20:21.560Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I participated in my first Humanities Hackathon called <a href="http://codexhackathon.com/">CODEX</a>, organized by Jennifer 8. Lee from <a href="http://plympton.com/">Plympton, a literary studio,</a> and is now in its third installment. The hackathon took place on the 3rd floor of the prestigious MIT Media Lab building in Boston.</p><p>I will be writing a couple of posts about my experience at the hackathon and the project that I worked on.</p><p>This first piece is a photographic travelogue of my time at the hackathon.</p><h3><strong>Snow Covered Campus</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7JKoA-EJMiM16Kbri0Ippw.jpeg" /><figcaption>A view of MIT Campus from the hotel</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LCFg7990qMkuJAKaruujOQ.jpeg" /><figcaption>In flight Entertainment</figcaption></figure><p>I took a red eye flight from San Francisco and did not sleep on the plane as I remained utterly absorbed in Dostoevsky’s world.</p><p>I arrived on the morning of Friday, February 10th and after a quick breakfast and shower went out for a walk to explore my surroundings. I found the campus completely abandoned and it turned out that classes at both MIT and Harvard had been canceled due to the severe and recurrent snow storms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PXtewirQP5rNerisR8QMmg.jpeg" /><figcaption>The streets of MIT</figcaption></figure><h3>Ready..Set..Party</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jjo15vUBEUleEcECs1KhXw.jpeg" /></figure><p>CODEX had organized a fun opening night party on Friday with lots of food, drinks, and MIT Press book giveaways. Along with writing our names on our name tags, we also had to write our favorite book. This definitely turned out to be a great conversation starter as I met many new people and had great conversations with them about their beloved books and authors. Currently enrolled in a course on Southern writers, I chose William Faulkner’s <a href="https://www.goodreads.com/book/show/77013.As_I_Lay_Dying?ac=1&amp;from_search=true">As I Lay Dying</a> as my favorite book for the evening. After having closely read three of Faulkner’s novels, I feel as if I have been living amongst his characters in his fictional Yoknapatawpha County.</p><p>Later in the evening MIT Libraries director, <a href="https://chrisbourg.wordpress.com/about/">Chris Bourg</a>, gave a wonderful talk about the serendipity of reading, the growth of digital libraries, and democratizing access. Chris joined MIT in 2014 after serving as an Associate University Librarian for public services at Stanford.</p><h3><strong>Saturday, February 11 — Hack DAY 1</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2xuu0mds00A63hu5N6ZI3Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HIZyt1C9G40UShkKdSG6RA.jpeg" /><figcaption>MIT Media Lab; Photo at the entrance of the MIT Media Lab of the iconic living room of MIT AI Professor Marvin Minsky</figcaption></figure><p>The hack day began promptly at 10 am. I arrived around 9:45 am and was surprised to see the room already full with eager hackers. I ate a hearty meal of pastries and coffee to fuel myself for the long day ahead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g57Z9Pb315RgFTeYw4SYmQ.jpeg" /><figcaption>Morning Presentations</figcaption></figure><p>The morning officially began with a word from a few of the sponsors and presentations about potential projects and ideas. It was interesting to see that many people in industry and academia are trying to solve similar problems in Digital Humanities. Hence CODEX serves as a great platform for everyone to combine their efforts and come up with innovative solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*glRFItX3SGC7962r1-bXMg.jpeg" /><figcaption>Paper Prototype of Influence Tree</figcaption></figure><p>For the hackathon project I decided to build a web visualization of authors influence. It seemed like an idea that would be easily accomplished in the short span of the hackathon. Using the tools provided by the Codex organizers, I spent a few minutes building a paper prototype.</p><p>The ping pong ball in the middle represents a searched author by the user and the green dots around the ping pong ball stand for the authors that influenced the searched author. Upon hovering on the green dots, a dialog, indicated by the yellow post it notes, will open up and reveal a short bio of the green dot authors.</p><p>I ended up naming the project <em>Influence Tree</em> and will publish another post about the details of the project.</p><p>We were served a sumptuous lunch and a hefty dinner. There were also a considerable number of snacks available throughout the day.</p><p>I was able to get most of the code working by the end of the day. We had to clear out the room at 10pm but I was still buzzed from hours of intense coding. I decided to spend some time walking around MIT Campus before heading back to the hotel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PWnZ63-_XC9dXoW-xEUY6w.jpeg" /><figcaption>Activism@MIT</figcaption></figure><p>I was pleasantly surprised to see many art installations, posters, and events inside the campus buildings in regards to the current political situation.</p><h3>Sunday, February 12 — Hack DAY 2:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vZ7dazRMZejIc1wY-XK7ng.jpeg" /><figcaption>Last hours of coding</figcaption></figure><p>Day 2 started at 9 am but I arrived close to 10 am as I had gone to bed around 4 am. I was not adjusting too well with the coastal time difference. In the morning I made a few minor adjustments and mainly worked on the presentation as we had to submit our final projects on D<a href="https://devpost.com/">evpost</a> by 2 pm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U75mVRU259zoyNlEyMvVBw.jpeg" /><figcaption>SWAG!</figcaption></figure><p>The swag for this hackathon was every book lovers dream. Not only did they give away books by notable presses but also had loads of goods by <a href="https://www.outofprintclothing.com/">Out of Print Clothing</a> and <a href="https://www.litographs.com/collections/t-shirts">Litographs</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wTYF7almqrudVweby5Ezbw.jpeg" /><figcaption>Final Presentations</figcaption></figure><p>The presentations started at 3 pm and lasted two hours. There were a total of <a href="https://codex2017.devpost.com/submissions">23 projects</a> that were presented and I found each idea to be very clever and imaginative. I will publish another post about these projects to give a taste of the kind of things that are being worked on in the field of Digital Humanities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IY08Qg9AyNJZNOHBfkBrGw.jpeg" /><figcaption>Stormy Boston</figcaption></figure><p>Another snow storm started around the afternoon and resulted in the cancelation of all evening flights. I had to rebook my flight and hotel and ended up spending an extra night in Boston.</p><p>We had to clean up after 5pm and said our last goodbyes to everyone!</p><p>CODEX was an amazingly energizing and fulfilling experience. It was wonderful to interact with likeminded tech bibliophiles and gain insights about current practices and tools utilized in Digital Humanities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vle9g8q43i2TwuvIbMVRzQ.jpeg" /><figcaption>Boston’s famous clam chowder</figcaption></figure><p>The extra night in Boston gave me the opportunity to try Boston’s famous clam chowder. I was initially a bit disappointed that I would be leaving Boston without tasting its speciality. And just like the CODEX Hackathon, it certainly did not disappoint!</p><p>In my next post about CODEX, I will write in detail about my project <em>Influence Tree</em> and also talk about the other projects that were presented at the hackathon. So Stay Tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e091a3990b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/a-photographic-journey-through-a-literary-hackathon-7e091a3990b3">A Photographic Journey through a Literary Hackathon</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Writer’s First Hackathon]]></title>
            <link>https://medium.com/codex-hack/a-writers-first-hackathon-63d7913ec9c1?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/63d7913ec9c1</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[mit]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[kate mulley]]></dc:creator>
            <pubDate>Thu, 16 Feb 2017 04:23:04 GMT</pubDate>
            <atom:updated>2017-02-16T04:23:34.675Z</atom:updated>
            <content:encoded><![CDATA[<p>I discovered the <a href="http://codexhackathon.com/">CODEX Hackathon</a> in a way that seems very fitting in hindsight: a girl I knew in high school (but was never friends with) posted about it on Twitter.</p><p>I am a playwright, an occasional poet, and a dabbler in other media. I applied for CODEX because I had heard the <a href="https://www.media.mit.edu/">MIT Media Lab</a> was cool and I thought it might be fun to stretch my brain for a winter weekend.</p><p>The following morning, I was accepted.</p><p>In the theater, you spend hours (or days) writing an application and if you’re lucky you get a rejection letter 6–9 months later. So this seemed like an auspicious start.</p><p>When I told (non-tech) friends about this literary hackathon I was attending they were immediately skeptical.</p><p>Them: “What’s a hackathon?”</p><p>Me: “Uh…. It’s like a weekend where you code and solve problems?”</p><p>Them: “Do you code?”</p><p>Me: “No.”</p><p>Them: “So why are you going?”</p><p>Me: “I’m a writer! I worked in publishing and for an independent book store. They also want people who are book people, not just hackers.”</p><p>Them: “Huh. Ok.”</p><p>I arrived at the MIT Media Lab (early) on Saturday morning with no plan. I did not know what I could offer this hackathon, but I was game to try anything. I whipped out my MacBook Air and sent some work emails so that I would look like I fit in, but when people started trickling in they were not hiding behind laptops, they were actually talking to one another. My attempt to fit in was perhaps misguided. I closed my laptop and talked with the women at my table. One was studying Computer Science and Journalism at Columbia. The other works for the <a href="https://dp.la/">Digital Public Library of America</a>. They seemed like exact embodiments of this hackathon. Unlike me.</p><p>After morning presentations and pitches from other participants I still felt at sea. Words I didn’t know and couldn’t define were bandied about like I was in a foreign country and I had no idea how my skills might help anyone. No project seemed to need the expertise of a playwright/publisher/shop girl. Perhaps I should just pack up my computer and pretend I never showed up in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-rGSg4wxFHCcXs8rB76Fsg.jpeg" /><figcaption>Brainstorming!</figcaption></figure><p>Luckily there was a design meeting for other stragglers, where we did some brainstorming and landed on some possible lines of inquiry related to books and reading. My group didn’t initially have one sole shared passion, but we had good group chemistry and were able to come up with a series of questions that felt like a statement about what we were interested in. Simply put, we wanted to make an Instagram for books, a way for people to discover books through a means other than reviews and Amazon. A way for people to use their own <em>creativity</em> to share feelings about a book. We first dubbed our project “meme girls” and then settled on “bookstagram” and got to work.</p><p>We decided our app’s target audience was teenagers and thought about all the ways teen readers might use images and text to share a book they had read with friends and strangers. I created “characters” who might use the app (Ana, Morgan and Maddie). I did research on books and found images and quotations. I had finally found a use for my skills. If there’s anything I’m unequivocally good at, it’s internet research.</p><p>Around dinner time we learned that a similar app already existed (not to be named here) and we lost a bit of steam. All four of us were surprised not to know about this app already, but eventually let the knowledge of the “competition” fuel us through to the end of the night. By 10 pm we had the structure of a PowerPoint presentation, the beginnings of a demo and front-end design (I am pretending to use these phrases correctly). Our bookstagram programmer, Chris, asked me if I felt like I worked at a start up as we walked to the T.</p><p>I responded, “It’s a lot like theater.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYTwhadKua2k_GoOS_KXfw.jpeg" /><figcaption>Team Bookstagram</figcaption></figure><p>The next morning, as travel plans were thwarted by an impending storm, we made finishing touches on our demo, PowerPoint, and design. We talked about books and our jobs and other hackathons. We laughed a lot, followed one another on Instagram, and casually sidled up to the swag to check it out.</p><p>By the end of the weekend we had spent almost 20 hours together, eaten four meals together, and presented something we were proud of and (somewhat) invested in. I cannot imagine a better experience at a first hackathon.</p><p>I rode the Red Line across the Charles to catch a bus back to New York (with banned book socks and a new book!) amazed at what I had learned and what we had accomplished as a group. Monday morning, after seeing my posts on Instagram and Facebook, a friend from London sent me a WhatsApp message to ask if I was leading a secret life working for a start-up at MIT.</p><p>I wish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63d7913ec9c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/a-writers-first-hackathon-63d7913ec9c1">A Writer’s First Hackathon</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reading through a Different Pair of Glasses]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codex-hack/reading-through-a-different-pair-of-glasses-1af01ecb4897?source=rss----3a818604ad72---4"><img src="https://cdn-images-1.medium.com/max/1656/1*huWM4FqsdpqxwgyxgFrg7w.png" width="1656"></a></p><p class="medium-feed-snippet">This past weekend, I attended the CODEX Hackathon at the MIT Media Lab. I love this hackathon because of its interdisciplinary nature &#x2014;&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/codex-hack/reading-through-a-different-pair-of-glasses-1af01ecb4897?source=rss----3a818604ad72---4">Continue reading on CODEX HACK »</a></p></div>]]></description>
            <link>https://medium.com/codex-hack/reading-through-a-different-pair-of-glasses-1af01ecb4897?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/1af01ecb4897</guid>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[augmented-reality]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Navraj Narula]]></dc:creator>
            <pubDate>Tue, 14 Feb 2017 20:52:26 GMT</pubDate>
            <atom:updated>2017-02-14T20:52:26.142Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Surfing the Contrails of the CODEX Hackathon]]></title>
            <link>https://medium.com/codex-hack/surfing-the-contrails-of-the-codex-hackathon-7e0fa10d1542?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e0fa10d1542</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Brendan Schlagel]]></dc:creator>
            <pubDate>Mon, 29 Feb 2016 13:06:01 GMT</pubDate>
            <atom:updated>2016-03-01T02:12:32.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pbmzm5GRyjq6bp-UWMb37w.jpeg" /></figure><h4>The true value of a hackathon isn’t the output of a weekend’s work — it’s how the experience changes your perspective.</h4><p>I recently attended my first ever hackathon — and the effects have lingered in surprising ways.</p><p><a href="http://codexhackathon.com/">CODEX</a>, hosted this winter at the <a href="http://media.mit.edu/">MIT Media Lab</a>, has a unique literary bent: it’s billed as a community of folks who want to imagine the future of books and reading.” As someone excited about technology and storytelling, libraries and information, design and education, I found the premise to be right up my alley — a perfect first hackathon if there ever was one.</p><p>On my bus ride from NYC to Boston that cold January morning, I thought a bit about what to work on, how to spend my time wisely and make the most of the experience. I didn’t entirely know what to expect.</p><p>Looking back on the experience, it wasn’t an unmitigated success according to how I thought hackathons were <em>supposed</em> to work — I didn’t leave with a mind-blowing product built, or an instantly-formed new network. But reflecting further, I did get a lot out of it, in ways I didn’t necessarily expect.</p><h4>Not Your Typical Hackathon; Not Your Typical Hacker</h4><p>Here’s the standard hackathon model: people (mostly technical people) break up into teams, each of which hacks together a rough project over the course of a weekend and demos it at the end. Then everyone disperses; a few projects live on but by and large entropy takes hold. In some respects it all looks a bit aimless, with an uncomfortable lack of permanence.</p><p>Me? I’m now several years out of Yale, working at the intersection of media production, education, and niche web business, and doing a lot of writing and side projects. I know how to put together videos and websites, but I don’t exactly self-identify as a “hacker”. And CODEX billed itself as something very different from your average hackathon.</p><p>At the event, after a whirlwind design thinking exercise, I did join a team. We volleyed interesting ideas about personalized on-demand annotations for contextual reading. I spent a lot of time working with some great people.</p><p>For me, however, that wasn’t actually the most valuable part of the hackathon. As Saturday morn turned to Saturday eve, and the sun soon rose on Sunday, I found myself exploring a kind of alternative shadow hackathon in my own mind, alongside and intermingled with the group work that divided my attention. I spent much of the time thinking through some of my own ideas, and I came out of the weekend with a renewed focus and energy.</p><h4>Leaving With Artifacts of Process, Not Product</h4><p>I may not have used my time at CODEX as effectively as possible, partly due to my hackathon inexperience, partly due to chance, and (if I’m being honest with myself) partly due to fear of committing to my own ideas.</p><p>However — however! — on the bus ride back home, Sunday night, as memory of the immediate artifacts receded, I felt the hackathon’s lingering effects. I felt its momentum, the way it nudged me onto unforeseen vectors, and accelerated ones I’d previously let lie dormant. As I reflected, I realized that CODEX ultimately helped me crystallize and build on some projects I’ve been toying with, and I’m excited to continue pursuing them.</p><p>I’d like to share some of the ways that seemingly-small fragments of this experience shaped my thinking, and offer some thoughts for how I might direct this personal momentum going forward.</p><h4>Only at CODEX!</h4><ul><li>At CODEX, I met a few whip-smart librarians, working on the cutting edge of the field. I was also exposed to a bevy of digital library brilliance I’d never encountered before — one great example: the <a href="http://dp.la/">Digital Public Library of America</a> — and this inspired me to start researching awesome and obscure digital collections, with the goal of curating and highlighting some of the best.</li><li>Witnessing all the incredible technical expertise unevenly distributed throughout the crowd of CODEX participants was at once inspiring and humbling. This showed me just how sparse my knowledge is in many areas, and how much potential lies beyond what I’m even aware of (case in point: <a href="https://www.wikiwand.com/en/Natural_language_processing">natural language processing</a>!) But at the same time, it hammered home just how much is possible in a very short period of time when the right mix of skills align with focus and creativity.</li><li>I was exposed to a heap of amazing projects old and new — from awesome APIs to world-class working groups to incredible ongoing research to audacious hacks. CODEX was great about assembling a great, and diverse array of people and interests. From the <a href="http://airtable.com/">Airtable spreadsheet-as-database API</a>, to the remarkable digital archives of the DPLA (linked above), to Kickstarter’s publishing project outreach, to the “Gitenberg” project bringing Project Gutenberg to Github, potential saturated the air.</li><li>During the hackathon, I participated on the “subTEXT” team, exploring ways to create an enhanced reading experience by crawling for contextually relevant information and bringing that information to the reader in an unobtrusive and personalized manner. While we didn’t end up with a working product (unbalanced team; technically overambitious; oh well!) it was nonetheless a very interesting area to think about and design. And it was great to be exposed to some of the sorts of things that such a project, brought to fruition, would necessarily entail.</li><li>The rigid constraints and accelerated pace of the hackathon helped me think more pragmatically about some of my own projects. For a handful of project seedlings that have until now existed mainly in my head, I came away from CODEX with concrete ideas for how I could start to actually build something tangible. I’ll discuss these in more detail below!</li></ul><blockquote>Here are some of the things I’ve come away from CODEX inspired to work on further:</blockquote><h4>Library Library</h4><p>I want to curate a digital library…of libraries. Or parts of them, at least. This would be not just a listing of different libraries around the world, but a focused collection highlighting specific collections that are particularly unique, interesting, and accessible — a portal to a rich variety of free information that someone browsing otherwise might never discover.</p><p>At CODEX, I started researching what sorts of things I could highlight. There are (surprise, surprise) about a bajillion great candidates. Things like: biological libraries of seeds or species; the digital bookshelves of Project Gutenberg; NYPL’s online collections (included exciting new public domain material); and the most intriguing bits drawn from the Internet Archive, World Digital Library, DPLA, Smithsonian, Library of Congress, and various great university libraries. Plus…all kinds of Internet esoterica like <a href="http://www.thermopedia.com/">Thermopedia</a> (“resources on heat and mass transfer, fluid flow and thermodynamics”) or the <a href="http://cervantes.tamu.edu/V2/CPI/iconography/index.html">Textual Iconography of Don Quixote</a>, or the <a href="http://oaktrust.library.tamu.edu/handle/1969.1/2490">Geologic Atlas of the United States</a>.</p><h4>Personal Canon a.k.a. “Canonize.me”</h4><p>I’m very interested in personal digital libraries, and in particular, the idea of one’s “personal canon” of important, influential, formative texts and media.</p><p>I’ve been thinking about what tools and methods — from self-hosted wikis to tagged Pinboard bookmarks — can be used to build and navigate them. Something I’d particularly like to build is a simple framework for someone to showcase their own “canon” (inspiration: <a href="http://davidcole.me/canon/">http://davidcole.me/canon/</a>). This would be a simple yet powerful way to display your résumé of influences and offer a peek at the threads leading to your worldview.</p><p>I’d like to make this an open-sourced template (side benefit: learn how to use Github) and perhaps further explore ways to use Pinboard, which I love. Along with this, or as the next stage, I’d like to host a list collecting various examples of personal canon pages, along the lines of Derek Sivers’ “<a href="http://nownownow.com/">/now page</a>” movement, or Diana Kimball’s “<a href="https://github.com/dianakimball/mentoring">/mentoring movement</a>”. This could include instructions for assembling a “personal canon” — and could even be one smaller part of a simple (but opinionated) personal website template.</p><p>I’ve worked more on creating V1 of my own Personal Canon over the past few weeks — <a href="http://brendanschlagel.com/canon/">here’s what I’ve got so far</a>!</p><h4>Antilibraries</h4><p>I’ve been working on a project called “Antilibraries”, about the vast landscape and potential of unread books — curating the best, with the goal of exploring new ideas and areas of the map. These are recommendations of books not necessarily to read, but to be aware of, so we can better explore the adjacent possible of the ideas they contain.</p><p>So far I’ve made a website for the project (blog with short writings about 50+ books in my personal antilibrary) and started a newsletter to highlight these (around 25 subscribers). But I’d love to take it further. A couple ideas:</p><ul><li>Some kind of podcast (to discuss others’ antilibraries)</li><li>Guest-curated book lists w/ interesting people</li><li>A digital book club (whatever that means) for people to tackle their antilibraries together</li></ul><p>This project has evolved over a couple stages already, and I’m not fully sure where it will go next, but I have some directions I’m excited to explore.</p><h4>It’s Not About What You Make, It’s About How It Changes YOU</h4><p>Hackathons are great birthing grounds for emergent phenomena.</p><p>I’m beginning to realize that as a category of event, they seem to be more about process than outcome. Despite culminating in prototypes and presentations — artifacts of hard work and concerted thinking — much of their value actually lies in what you’re exposed to along the way, and how the experience can nudge and reshape your thinking.</p><p>Much of the power of an event like CODEX comes from what it inspires — in how its influence extends into the future and permeates work to come.</p><p>This means that one useful way to approach a hackathon is to focus on collecting and banking as many relationships, ideas, and conceptual frameworks as possible over the course of the event. And a valuable alternative to focusing on final output can be found in letting your mind wander, picking up fragments to save for later, and generally treating the whole thing as a learning experience to the greatest degree possible.</p><p>If I were to go back in time and do CODEX all over again, I’d no doubt do it differently. And that’s part of the beauty of this kind of chaos directed toward creative ends — ultimately it doesn’t matter what you end up with, it matters how it changes <em>you</em>.</p><p>Before CODEX, I had many side project ideas, but little direction for how I might actually change experiences of reading, browsing, curating, or otherwise interacting with the written word. Now, I’m a bit more confident I can make things that matter.</p><p>The shift in perspective is subtle, but it’s the accretion of just such small shifts that shapes us.</p><p>I’m glad I went, and can only hope I’m able to work this ethos of experimentation into my daily life. And if I start to feel the hackathon spirit diminish, well…I’ll be back next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e0fa10d1542" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/surfing-the-contrails-of-the-codex-hackathon-7e0fa10d1542">Surfing the Contrails of the CODEX Hackathon</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four Reasons Startup Founders Should Go to Hackathons (It’s Not What I Originally Thought.)]]></title>
            <link>https://medium.com/codex-hack/four-reasons-startup-founders-should-go-to-hackathons-it-s-not-what-i-originally-thought-8194db5d219c?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/8194db5d219c</guid>
            <dc:creator><![CDATA[Ted Benson]]></dc:creator>
            <pubDate>Tue, 28 Jul 2015 18:44:02 GMT</pubDate>
            <atom:updated>2015-07-29T01:21:50.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyLb0pyaa2ZZvEZVu-tIIQ.jpeg" /><figcaption>Our team at CODEX Hackathon: a museum curator, a writer-translator, MIT grad student and a start-up founder.</figcaption></figure><p>As a startup founder, you’re constantly making decisions about how to spend your scarce time. Weekend hackathons can be a hard sell from this perspective: two whole days that are seemingly neither on your company’s critical path nor a break from sitting at a computer.</p><p>But after spending a weekend in late June at the <a href="http://codexhackathon.com/">CODEX Hackathon</a> in San Francisco, I think I’m a convert. Hackathons can be a wonderful way for founders to re-kindle their creativity and gain a lot of unexpected professional insights too.</p><p>CODEX was weekend-long event dedicated to hacking literature, which is already cool and creative to start. But what really won me over was that the organizers used the sponsorship funding they raised to fly in interesting participants rather than simply offer a large cash prize pot. As a result, the crowd was varied: MIT researchers, language translators, museum curators, Google engineers.</p><p>In my idealized dreams, I<em> </em>thought CODEX would be an opportunity for my startup <a href="http://www.cloudstitch.com/">Cloudstitch</a> to find eager users of our product (and it was — I’ll post about the cool things we built another time). Our company, which is in the current Y Combinator batch, helps developers power websites with Google Spreadsheets instead of databases, which is a perfect fit for prototypes and hackathons.</p><p>So our plan, looking forward to the event, was all about <em>build build build. </em>We prepared some spreadsheet-powered <a href="http://www.cloudstitch.com/project-templates/recovering-the-classics-api/api">literary APIs</a> and example starter projects, like an <a href="http://apps.cloudstitch.io/project-templates/book-cover-wall/">infinite wall of books</a> and a <a href="http://www.cloudstitch.com/project-templates/featured-guests">conference attendee widget</a> in hopes they would serve as useful launching pads.</p><p>But looking back at the event afterwards, was really surprised me was how much I personally got out of the experience as a founder<em>. </em>So here are four reasons why you, as a founder, should consider going to a hackathon.</p><h3>1. You’ll be reminded creative goals, not technology details, are what’s important</h3><p>Each company has their brand of hammer and spends time finding people who have the right nails to hit. And a hackathon reminds you that this is a very narrow mentality.</p><p>Despite being part of the kickoff-pitch lineup of talks in the beginning, I couldn’t help but see a bit of comedy in our situation. We wanted everyone to use Cloudstitch to power their prototype’s data with spreadsheets. MailChimp wanted everyone’s prototype to send mail to people. Dropbox wanted people to use the Dropbox API. I don’t mean this in a cynical way: our job as sponsors is to provide an arsenal of tools and support for anyone who wants to use them. And we all did a great job of that, I think.</p><p>But making the rounds and chatting up people to see if you can help is a powerful reminder that, at heart, creativity, not tooling, is the powerful driver of the innovation. The goals you admire while making the rounds have nothing to do with implementation. “I want to help book worms find love based on their reading list” “I want to help people finish the books they’ve started” “I want to connect people to the stories that take place in their own cities”</p><p>If you’ve fallen into the trap of clutching your hammer and looking for nails— and I certainly have — a hackathon is a vitamin shot back into that creative space where technology is simply a detail in service of creative goals.</p><h3>2. You’ll have a chance to use your product in an unexpected way</h3><p>Building on the importance-of-creativity thought, you can almost be guaranteed that the way you thought people would want to use your project will not be how they actually use it. This is probably somewhat true of products in general, but to get to see it in the condensed space of a weekend is refreshing and eye-opening as a founder. At the very least, you will leave with the excited feeling of a parent seeing their child do something they never directly taught them.</p><p>Take the team I spent the weekend hacking with: <a href="https://twitter.com/digitalanika">Anika Gupta</a> of MIT, writer-translator <a href="https://twitter.com/arendse">Arendse Lund</a>, and Eric Gardner of Getty. We built an eBook that layered rich ambient experience onto plain text: subtle background images and maps behind the text; ambient music and sound effects; photos of relevant places in the margin. All of it was meant to subtly enrich the feeling of story immersion without going too far and making it feel like a magazine. <a href="http://egardner.github.io/Baskervilles/chapters/ch05.html">You can read a demo of the Hound of the Baskervilles we made here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YwHkhEyxNAV0atAcDIHiw.png" /><figcaption>I never would have thought our Spreadsheet-based development platform would have relevance to eBook authoring.</figcaption></figure><p>Now all this was powered by nothing more than the raw text of the book combined with a very clever and simple spreadsheet. In one column you paste a sentence in the book, and in the next column you paste what kind of rich media accompaniment that sentence should queue up for the reader. But if you asked me the week before if Cloudstitch had relevance to eBook authoring, I probably would have quickly said, “No — we’re really focused on people who have structured data to publish”.</p><h3>3. You’ll get to see many different pitching and demo styles</h3><p>I think the pitches at the end of a hackathon are far more useful to observe than those at a pitch competition. First of all, hackathons presentations are closer to what a founder does than a pitch competition because there’s sweat and love involved. You’re excited about an idea, have worked hard to prove it out, and now you want to make the case to others in an environment crowded with others doing the same thing.</p><p>Secondly, hackathon pitches are essentially marketing pitches, whereas pitch competition pitches are heavily business-plan focused. If you subscribe to the Dave McClure school of thought, you’ll find way more utility watching marketing-style pitches.</p><p>In the final hour or two of any hackathon, you’ll see a range of presentations. Slick pitches based entirely on design mockups. Data-driven pitches that argue for the feasibility of a product. Demo-based pitches. Slide-driven pitches. Narrative-driven pitches. Demos that crash. Demos that leave eveyone with tears of laughter. And there is guaranteed to be someone trying to sound like Steve Jobs, with intonations and pauss (identifying this person definitely be incorporated into some sort of hackathon drinking game).</p><p>You probably fall into one of the pitch categories above. It is important that you occasionally get the chance to see many different pitch styles together so that you can reflect on your own style.</p><h3>4. Your memory of the event doubles as reminder of how important it is to finish your product and ship it</h3><p>The group emotion of a hackathon project roughly follows this arc:</p><ul><li><strong>25% Milepost: </strong>“Okay, it’s becoming clear we need to limit our scope…”</li><li><strong>50% Milepost: </strong>“This is really turning into a cool prototype.. now if only we can actually get it to work”</li><li><strong>75% Milepost: </strong>“Wow, just think if we followed through on this! So many people could use it”</li><li><strong>While saying goodbye:</strong> “So cool to meet you guys — let’s really stay in touch and see if we can work on this!”</li><li><strong>Two weeks later</strong>: “Gosh…if only there was time in the day to finish that up.”</li></ul><p>And that’s just fine. Most hackathon projects are destined to be Tibetan sand paintings. Beautiful collaborations that arise through hard work and then, in an instant, are left for the wind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDvQbb5Fp2Ic6yPdeK7x4Q.jpeg" /><figcaption>Most hackathon projects are destined to be Tibetan sand paintings.</figcaption></figure><p><em>But your startup must not be a sand painting. </em>So let the memory of “gosh, if only we had time to finish that hackathon project” be a powerful reminder that it’s the things we ship — not build — that create a lasting company. Your professional life as a founder is the sum of how you spend each week, and you must make sure that those weeks are spent not just starting things, but finishing them too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8194db5d219c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/four-reasons-startup-founders-should-go-to-hackathons-it-s-not-what-i-originally-thought-8194db5d219c">Four Reasons Startup Founders Should Go to Hackathons (It’s Not What I Originally Thought.)</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Run a Collaborative Hackathon: The Cheatsheet]]></title>
            <link>https://medium.com/codex-hack/how-to-run-a-collaborative-hackathon-the-cheatsheet-72cb24cf2bcb?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/72cb24cf2bcb</guid>
            <category><![CDATA[codexhack]]></category>
            <dc:creator><![CDATA[Jennifer 8. Lee]]></dc:creator>
            <pubDate>Mon, 13 Jul 2015 22:19:31 GMT</pubDate>
            <atom:updated>2015-07-14T01:09:55.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HUnip0GN4-b0dnKkNGpmCQ.jpeg" /></figure><p>A hackathon is basically like a two-day party with programming. You want people to feel like there will be good people, good food, good space, good vibes all around.</p><p>One thing the publishing industry has working strongly in its favor: people of all disciplines <em>love</em> books. They love reading and love libraries. There is both enthusiasm and concern for the industry as it progresses through a digital transition.</p><p>But the challenge in publishing: the entire ecosystem has to move together to get into the future — the writing, the engineering, the retail experience, the curation, the legal constraints. It’s like the coordination needed in a three-legged race — only one run by spiders tied together.</p><p>Our goal with the <a href="http://codexhackathon.com/">CODEX Hackathon</a> was to nurture the face-to-face relationships that we’ve come to realize are so important in publishing from our years working on <a href="http://plympton.com/">Plympton</a>, a literary studio. This is an industry based on individual trust (the place to see that in action is at the <a href="http://www.buchmesse.de/en/fbf/">Frankfurt Book Fair</a>, where you can watch a giant <a href="http://harpers.org/archive/2009/03/the-last-book-party/">pas-de-deux of meetings after meetings</a> in the great halls).</p><p>We wanted people to leave CODEX with relationships that they could build upon in the future — whether between app developers and literary journals, or Big Five publishers and design-thinking folks.</p><p>At the end many attendees said CODEX Hackathon was the funnest hackathon they’d ever been too — well-organized, collaborative, good food, interesting and diverse people, useful tools, and an inspiring space.</p><p>But it took <em>a lot </em>of effort from a lot of folks to put it together (and a fair bit of stress, once we discovered the hackathon was the same time as Pride Weekend). So we wanted to capture some of our learnings for others in the spirit of having more well-run collaborative hackathons in the world.</p><p>We took inspiration from the excellently executed <a href="http://hackingjournalism.com/">Hacking Journalism</a> event at Condé Nast in New York in January (which had <a href="https://www.rememberlenny.com/">Lenny Bognodoff</a> and Jeanne Brooks among its organizers). So this is a more formalized guide we would have wanted before we started planning.</p><h4><strong>Strong Branding and Theme</strong></h4><p>We wanted a good name for the hackathon — one that would have a shelf-life since we hoped to hold more than one, if all went well.</p><p>After a bit of brainstorming on Slack, we came up with CODEX, which worked on many levels for all the different constituencies. The “codex,” the bound book, has strong literary roots. Also “Code X” gives it a whiff of programming nerdiness. Last, there was a historical connotation of innovation. The invention of the codex allowed for random access to data for the first time. Before that, the scroll only allowed for sequential access (The developers loved this fact).</p><p>So with name in hand, we asked designer-developer <a href="https://twitter.com/allanlasser">Allan Lasser</a> to create a logo. We needed the design to do a lot of things. First it had to accommodate both interpretations of “codex” and “code X.” It also had to keep open the possibility that CODEX brand could expand beyond hackathons. (Fellowships, conferences, etc.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*vL_TV8vE9xM7ooTacd5ozw@2x.png" /><figcaption>CODEX logo by designer-developer Allan Lassar</figcaption></figure><p>Allan came up a great logo concept — pages linked together, each with a single logo. It was clean, evoked publishing and also intertwined the “Code X” interpretation of the event. It gave us the flexibility to extend that logo to other CODEX events.</p><p>We went back and forth on the font choices and ultimately settled with <a href="https://www.google.com/fonts/specimen/Roboto">Roboto</a>, because looked the best skewed and also came with a big font family. Then he put it against a colorful background with our Recovering the Classics covers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YB2ukpoA7Ik2g238Tcyj9w.png" /></figure><p>We also used the single X-on-a-page as the <a href="http://twitter.com/codexhackathon">avatar for Twitter</a> and other places (like Github). With logo in hand, we could set up a page on Splashthat.</p><p>Our developers insisted on having a theme, instead of being totally open ended. More Slack, we chose “connecting,” which was pretty flexible, but gave just a hint of guidance, for those who were looking for it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kox9vw0qnsLq8e-Sjd2guQ.jpeg" /><figcaption>Lots of screens rotating with CODEX and sponsor logos.</figcaption></figure><h4>Application Process</h4><p>We decided to have <a href="https://plympton.submittable.com/submit/42415">an application</a> (rather than registration) process for CODEX. Partially, this was because we had limited capacity — around 100, and we wanted to make sure we got good people. Also, it made applicants take their commitment to the hackathon more seriously. We basically loosely adapted the form from the <a href="http://hackingjournalism.com/">Hacking Journalism</a> event, with a few extra questions like “What’s your favorite book?”</p><p>The original application form was done on Wufoo, but we ultimately switched to <a href="http://submittable.com/">Submittable</a>, even though Submittable requires folks to register with name and email before they can submit form. We made the switch not only because Submittable was a sponsor and willing to help us set it up, but because it gave us a lot more control over the relationship with the applicants over time, and had an good review set-up. Plus, their roots were in literary journals.</p><p>We were initially resistant to forcing people to register before applying, because we felt it caused too much friction. But ultimately came to see the right choice. The Submittable CEO said that forcing the registration increased conversion by double digits. In large part, it was because applicants could save their forms in, which allowed them to come back later if it wasn’t finished.</p><h4><strong>Sponsors and Partners</strong></h4><p>We worked hard to get really good sponsors and partners for the hackathon, both in tech and literary world. On the literary side, we came in with the New York Public Library, the <a href="http://dp.la/">Digital Public Library of America</a>, and <a href="http://harvard.com/">Harvard Book Store</a> as partners, since we are working with them through our <a href="http://recoveringtheclassics.com/">Recovering the Classics</a> project. But we needed strong tech cred as well. GitHub’s generous offer to use their <a href="https://customspaces.com/office/DhXb6EKlE9/github-office-san-francisco/">beautiful space</a> (complete <a href="http://thenextweb.com/shareables/2013/09/07/githubs-new-office-includes-a-replica-of-the-oval-office/">with a replica of the Oval Office</a>) for an opening night pop-up gallery gave us a huge boost of tech cred. For all my stalking GitHub execs through investors and friends, I ultimately found success through just cold-applying through an online form at <a href="http://community.github.com/">community.github.com</a>. Mailchimp (<a href="http://mashable.com/2014/11/12/marchimp-mailkimp-meme/">Mailkimp</a>?) also was an early and generous sponsor. The other early tech cred came from Dropbox thanks to my one-time neighbor <a href="https://twitter.com/varenc">Chris Varenhorst</a>, who heads developer tools there. (This is where being based in Silicon Valley helps, because you just know these people).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQuy6ffHEj6xiq3SeAcxKA.jpeg" /><figcaption>Friday night pop-up gallery at GitHub with live music, dumplings, and literary cocktails.</figcaption></figure><p>Since we wanted to be inclusive, we made a big effort in making a range of price points that could work for everyone, from Fortune 500 companies to small bootstrapped startups.</p><p>We divided the organizations into sponsors and partners. Sponsors were entities that contributed money, whereas partners provided in-kind support rang from from data (<a href="http://publishersweekly.com/">Publishers Weekly</a>) to logistical organizing (<a href="http://www.chroniclebooks.com/">Chronicle Books</a>).</p><p>It took some thought and creativity in shaping the packages so you could tier the sponsorships appropriately. This generally meant allowing the higher-level sponsors to access the RSVP list, or offer a tool or a challenge, or give a longer talk in the intros. Basic sponsors were basically just showing a logo.</p><p>And just as with investing, when you have first money in, it gets a lot easier to get more. The <a href="http://knightfoundation.org/">Knight Foundation</a>, which has had done a lot of work with libraries, was the first to commit hackathon funding (Thank you George Martinez!). Once that was made, we knew we had enough money to at least pay for pizza for a hackathon for every meal, so we could host that. HarperCollins, which is one of the most innovative of the Big Five, joined in with a big commitment.</p><p>Ultimately we raised tens of thousands of dollars in sponsorship money in amounts ranging from $250 to $10,000. And we chose to use that money in a very strategic way — travel stipends.</p><h4>Publicity</h4><p>Once we had a critical mass of sponsors in hand, we felt confident in going public.</p><p>This part was stressful, and very much like throwing a party. What if you hold a hackathon and no one shows up? You will be judged. Also, we had to attract people locally and nationally, so needed a dual campaign.</p><p><a href="http://slifty.com/">Dan Schultz</a>, one of the CODEX volunteers, pushed it out to his MIT Media friends, Mozilla, and tech journalism circles both inside and outside the Bay Area.</p><p>We asked friends in the Bay Area to send it over open company email lists: Quora, Twitter, Stripe, IDEO, etc. (interesting to learn which companies don’t have open email lists!) I emailed CS professors at Stanford asking them to get the word out to their students. This proved fruitful as Stanford now has a neat new English+CS combo major.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*KzGJkWIBUML8-azuDjXQUA.png" /><figcaption>Asked Craig Mod to Tweet about CODEX</figcaption></figure><p>To get some national visibility among developers, we also asked John Resig (creator of Jquery) to <a href="https://twitter.com/jeresig/status/601408190148907008">tweet about CODEX</a>, as well as <a href="https://twitter.com/craigmod/status/601543469966888960">Craig Mod</a> (who has a huge book-innovation following). Both of those posts got a number of retweets and favorites. We even got permission from both of them to promote their Tweets via Twitter’s advertising system.</p><p>Then applications started rolling in. We knew it was a good sign when we started getting messages about the hackathon from the email lists we were on.</p><p>A key attraction was that we offered travel stipends.</p><h4><strong>Travel Stipends</strong></h4><p>Some hackathons use their money for big prizes (five-figure checks are pretty common). But given our goal of building relationships, we decided to take our sponsorship money and channel it towards travel stipends. Thanks to our sponsors, we were able to give out well over ten thousand dollars in travel stipends to folks from all around the United States and even internationally (Mexico and Canada).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*6KWWtDhAkiHlnKRug7-8_Q.jpeg" /><figcaption>A good number of Canadians were imported for the hackathon: from Toronto, Vancouver and Saskatoon, Saskatchewan. Canadians. They walk hidden among us.</figcaption></figure><p>One reason travel stipends help create a good hackathon. If you are pulling in folks locally for a hackathon, you often lose people on the Sunday, because they have other things to do — church, picnics, prior obligations. But if people have traveled in for the hackathon, it’s their main priority. They will be there. So by giving out dozens of travel stipends, it guaranteed we had a very dedicated core group.</p><p>A quick early offer of a $250 subsidy was often enough to tip interested folks into coming to the hackathon. When we first announced CODEX we didn’t know how much sponsorship money or demand we would end up with, so we were cautious in metering out the stipends. It was impressive how many people were able to leverage that initial $250. One person used our commitment to get work, a library, to pay for the rest of the trip.</p><p>We eventually were able to offer larger stipends in specific circumstances: if someone was willing to help be an organizer for the hackathon; if they were willing to specifically work on a sponsor challenge or tool; if they were filling a gap we had in our line up (a bookstore or a literary journal). At that point, our general rule was that we would pay for the roundtrip plane ticket, but that they had to find their own place to crash.</p><p>And some of our partners offered travel stipends targeted specifically at their communities. For example <a href="http://gitbook.io/">Gitbook</a> offered a generous $1,200 international stipend, which included housing, based on proposals. That was good for us, because the announcement of the stipends to their communities drove more awareness of the hackathon overall.</p><h4><strong>Diverse Backgrounds</strong></h4><p>We knew that in order to have a good hackathon we wanted people with different backgrounds: engineering (back-end and front-end), editorial (writers and publishers), design (graphic and UX), retailers (online and off-line). We were able to use our application process (done through Submittable) to keep an eye on the balance, and also use the travel stipends to curate and recruit folks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*80rlp9XauuMFy7gXdUfIcQ.jpeg" /></figure><p>Some of the non-tech folks were a bit nervous about never having “hacked” before. But we insisted that they were among the most important folks there, because they had a perspective on the problems and challenges the industry was facing. If engineers go off and try to tackle publishing from an engineering perspective, they come up with a limited number of projects.</p><p>Important. Get non-techies into a hackathon! They will often have the more interesting ideas and problems to solve.</p><p>What was lovely was the kind of developers and engineers we attracted. They were people who loved books! As one MIT PhD described it, “We’re humanities people trapped in a developer’s body.”</p><h4>Stanford d.School Workshop</h4><p>How do you get cool projects?</p><p>Some folks came into the hackathon with a team and idea in mind, but most were waiting to be inspired. So we needed to find a way to create good teams who could tackle interesting questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S3SSiPhrjkqRN8Ig3vL7yg.jpeg" /><figcaption>Erik Olesund of the Stanford d.school led a range of ice breakers and brainstorming exercises to start CODEX</figcaption></figure><p>We were super lucky to connect with <a href="http://dschool.stanford.edu/bio/erik-olesund/">Erik Olesund</a>, a fellow at the <a href="http://dschool.stanford.edu/">Stanford d.school</a> who started our hackathon by holding a design thinking and innovation workshop on Saturday morning.</p><p>In about an hour, Erik took our CODEXers from ice breakers to fully formed teams and ideas using Post-It notes, Sharpies, and a lot of pairing exercises.</p><p>This process was hugely useful, and one of the best ways I’ve seen a hackathon start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MsTac4f2FD2bDE2I9p_lWg.jpeg" /><figcaption>Post-It notes are key to brainstorming.</figcaption></figure><h4><strong>Tools, APIs, and Data</strong></h4><p>We made a specific push to get a <a href="https://docs.google.com/document/d/18fLZV_qd9IGaBxWDY4MJw4ELs8SPpidprvApmiVbkjk/edit#">variety of tools and data</a> for attendees to play with. These are the tech equivalent of construction paper, pipe cleaners, tinfoil, colored felt and markers. In combination things become really interesting.</p><p>But we wanted to have both editorial and tech resources. Editorially we got short stories, public domain classics, Recovering the Classics book covers, serialized novels. We also got reviews data from Publishers Weekly.</p><p>One thing that can make a hackathon appealing to programmers is to get early or exclusive access to tools that are not yet public. We were lucky in that a number of companies had new APIs that they wanted to test out and get feedback, including <a href="https://www.wattpad.com/codex/">Wattpad</a> and <a href="http://kb.mailchimp.com/api/article/api-3-overview">Mailchimp</a>. We also lobbied our engineering friends at Pinterest to get folks onto the whitelist for their API. Last, we pushed on some publishing startups to make their internal APIs public facing, including <a href="http://shelfie.com/">Shelfie</a> for their OCR ability and <a href="http://zolabooks.com/">Zola</a> for their Bookish <a href="http://bookishrecommends.com/codex_hackathon/bookish_recommeds_api.pdf">recommendation engine</a>. The Shelfie OCR API was of interest to me, because I’ve wanted to get a dating app based on books created ever since <a href="http://www.newyorker.com/books/page-turner/computer-find-me-a-book">I went to another publishing hackathon two years ago.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*O4ySeNFudvAWqy6TOfrtQg.jpeg" /><figcaption>Forkpad, a project from CODEX Hackathon, is built a new API from Wattpad and allows readers to “fork” stories and write their own fan fiction of fan fiction.</figcaption></figure><p>Basically, you get very powerful results once you start chaining the tools together. One of the most practical projects to come out of the hackathon was <a href="http://hackdash.org/projects/55904cb8db0166dd1b11da68">Goodshelf</a>, which is what you would get if Goodreads and Shelfie had a love child. Basically, the Shelfie API (which can take a picture of a bookshelf and return a list of books) combined with the Goodreads API (which allows you to add books to your bookshelf). As a result you could take a picture of a bookshelf and add those books onto Goodreads, which is easier than keying them in by hand, or taking pictures of bar codes.</p><h4>Beautiful Space</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_esAu0AYinaXp-l2idz-w.jpeg" /></figure><p>One perennial question for the hackathon organizer. To hack all night, or not? Part of the aesthetic ethos of the hackathon is to see skinny bodies sprawled out sleeping on the table in the middle of the night.</p><p>But it’s actually hard to find spaces that will allow you to stay all night for staffing and security reasons. My developer friends said that you need to stay open until at least 10 p.m. to get a good productive window after dinner. But it’s not necessary for folks to stay all night because of diminishing productivity. Rather you want to stay late enough on Saturday but open early on Sunday.</p><p>Also, you want to have a beautiful space that has reliable wifi, good breakout areas and a common area for presentations.</p><p>A few weeks into the planning CODEX we realized we had a major challenge. The ALA conference was at the same time as <a href="http://www.sfpride.org/">Pride Weekend</a>. That basically knocked out any spaces along Market Street because of the Sunday Parade (and my developer friends were insistent that you could not switch a space mid-hackathon). We never realized how many big tech offices are located just off of Market Street. This made for a very anxious scramble for a few weeks trying to find a place.</p><p>We were lucky to link up with <a href="http://codeforamerica.org/">Code for America</a> (in part because I bumped into its director, Jen Pahlka, in a neighborhood Ethiopian restaurant). <a href="http://parisoma.com/">Parisoma</a>, which hosts hackathons, was also a great option in SoMa.</p><p>CfA has a gorgeous space with great wifi, lot of outlets and plenty of breakout rooms, including a downstairs area with yoga mats. It was also located safely far away enough from the heart of the Pride Parade. And thanks to their ops people, they were able to have folks stay to host us until 11:45 pm Saturday night (enough time so the staff could take the BART home).</p><p>Highly recommend for anyone thinking of doing an event there.</p><h4>The Schedule</h4><p>Excluding our opening party on Friday night (which had no talks, purely social), the hackathon itself ran 10 am to 11:45 pm on Saturday and 9 am to 5 pm on Sunday (wanted to get them out before dinner).</p><p>We kicked off the morning with some simple talks from a mix of sponsors and partners with interesting tools. Then those who had a project in mind just started working, while the vast majority of folks went to the Stanford d.school workshop.</p><p>Catered meals were delivered, but there were no official meal breaks. During dinner on Saturday we held some longer, opt-in talks from <a href="http://kickstarter.com/">Kickstarter</a>, <a href="http://poeti.ca/">Poetica</a> and <a href="http://codex.press/">Codex Press</a> for a smaller crowd.</p><p>Presentations started at 3 pm on Sunday and ran for two or so hours. People broke for dinner, and then some folks reconverged for an afterparty at my place, which was only two blocks away from Code for America.</p><h4>Food</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jx2qCaFXSyAYsdrou0L_zA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/1*76pbw5BV1rPUP9AnbTE2hw.jpeg" /><figcaption>Arepas!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*ik3VTL4HuhpV1QtG_w_0zg.jpeg" /><figcaption>Malaysian food from <a href="http://www.azalinas.com/">Azalinas</a> in the Twitter building</figcaption></figure><p>We had <em>great</em> food, because a number of the organizers really cared about food (I’ve even written <a href="http://thefortunecookiechronicles.com/">a book</a> and produced a <a href="http://thesearchforgeneraltso.com/">documentar</a>y on food).</p><p>We basically gave <a href="http://twitter.com/zoelle">Zoelle</a> a budget to go find “not-white people food” and “not-lame” breakfasts. Since so many companies in Silicon Valley feed people all the time, we wanted something distinctive.</p><p>Our meals included Malaysian, Filipino, Chinese dumplings and pastries, arepas and late night deep dish pizza (gotta have second dinner on the Saturday night). The cost for the lunches and dinners were generally around $1200-$1500 for 100+ people. And we made an effort to use small emerging businesses where that was a significant catering order for them.</p><p>We supplemented the catering with snacks from Trader Joe’s and Costco.</p><p>Attendees keep mentioning about how yummy the food was and how well-fed they were. This is a list of the caterers we used.</p><h4>Presentations</h4><p>We wanted to use a single computer for the presentations to keep things efficient. We required everyone to register their projects on <a href="http://hackdash.org/dashboards/codex2015">Hackdash</a> as part of a nice dashboard we created for the event.</p><p>Doing so had the benefit of producing a single link that can be shared and circulated after the hackathon.</p><p>A lot of people showed up for the presentations, way more than were actually there during the heart of the hackathon (where were these people coming from? They weren’t hiding out in the basement).</p><p>We had more than 25 teams. We gave them each 3-ish minutes to present, no Q&amp;A. Some just did a slide presentation. Others used the video camera on the computer to project an iPhone app on the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3eylqf1hDoGDjrJ7fbhC2w.jpeg" /></figure><p>With that many projects, it took a long time to plow through them. Almost two hours. And then we were done.</p><h4>Prizes</h4><p>We gave out mostly book schwag from Litographs, Out of Print, and publishers. Some of our sponsors, like Mailchimp and Dropbox, also offered prizes specific to teams which used their projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XnDWHTG_TX51WyuaFFdUzQ.jpeg" /><figcaption>Book schwag, generously doanted by <a href="http://outofprintclothing.com/">Out of Print Clothing</a></figcaption></figure><h4>Final Thoughts</h4><p>In some ways, a hackathon feels like startup. It can look totally smooth from the outside even as you feel things are going wrong every which way from behind the scenes (coffee shortage, AV glitches, missing book shipments, canceled flights).</p><p>But at a certain point, if you throw enough interesting people together with a wifi and a mission, it just works.</p><p>We love our CODEX Hackathon experience enough that we’re going to do it again, January 8–10, 2016 at the ALA Midwinter Conference in Boston. Save the date. It’s going to be bigger and better next time around.</p><p>Questions? Email jenny[at]plympton[dot]com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72cb24cf2bcb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/how-to-run-a-collaborative-hackathon-the-cheatsheet-72cb24cf2bcb">How to Run a Collaborative Hackathon: The Cheatsheet</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts from making tools for literature]]></title>
            <link>https://medium.com/codex-hack/will-the-future-of-writing-be-more-like-software-49f2a6900ca9?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/49f2a6900ca9</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Pippin Lee]]></dc:creator>
            <pubDate>Fri, 10 Jul 2015 02:18:03 GMT</pubDate>
            <atom:updated>2015-07-10T18:50:06.518Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5moklcdrPhG6WmN-KC3sLw.png" /></figure><h3>How Literature and Code Overlap</h3><p>When we think about languages and how they evolve, it’s usually at the needs of the people that use them. If we want to share a bit of information, whether that be an emotion, or description — we can create a new collection of letters to form a new word. As long as another person has a common understanding of this combination of letters, we can now use our new word in <a href="http://number27.org/wb-language">sharing information from one mind to another</a>. Languages can be pretty neat this way, and can get even more descriptive if we talk about emojis.</p><p>Software, on the other hand, has overhead and accessibility issues. Sure, it also allows you to invent new meanings, and even create new languages — but currently it only evolves when you tell the machine to do something specific, and with correct details. This makes it tough for most to get involved and interested in seeing how the web, and computers will shape publishing going forward.</p><p><a href="https://twitter.com/maxbittker">Max Bittker</a> and I were lucky enough to spend the last weekend in June on the West Coast working along side folks who also care about a number of these issues at <a href="http://codexhackathon.com/">CODEX Hackathon</a>. CODEX billed itself as an event to play with the future of publishing, but was really just a good excuse for smart designers, developers, and publishers to come together to build things that asked an important question of the direction of reading.</p><p>So over that very frenetic weekend, we built <a href="http://forkpad.me/">forkpad.me</a> — a service that allows the remixing of stories on the popular writing site <a href="https://www.wattpad.com/home">Wattpad</a> — to help their community become better writers, and keep the web weird. Along the way we realized that the process of writing could take inspiration from the open source software development process. This idea lead us to asking these three questions, which helped shape the tool we wanted to build:</p><ul><li><em>What happens when writers are able to remix and reuse each others work?</em></li><li><em>What happens when a story is never “finished”?</em></li><li><em>What happens when a story can have multiple authors?</em></li></ul><p>Intrigued by this, Max and I asked ourselves how we could make a tool that could bring key aspects of Open Source Software (OSS) development to the writing and publishing process.</p><h3>Informality Will Rule Publishing</h3><p>One of the things Max and I love about the web is its ability to share information easily. Thanks to all the underlying technical protocols, we’re now able to build tools to reach many. When we showed up to <a href="http://codeforamerica.org/">Code for America</a>’s San Francisco office Saturday morning, we knew the community on Wattpad was something we could have a lot of fun with.</p><p>We were given <a href="http://www.wattpad.com/codex/">early access to the API</a> for Wattpad, a massive serial writing community <a href="https://www.wattpad.com/about">with over 40 million users</a> who collectively spend more than 900 million years on the Wattpad site each month (85% of it on mobile).</p><p>In the time you’ll spend reading this article, Wattpad will receive enough werewolf fan fiction to last the rest of your life, in addition to other fan fiction of all niches and all personalities. I personally recommend checking out the entire <a href="http://www.wattpad.com/story/30644165-50-shades-of-drake-drake-fanfic-series">50 Shades of Drake</a> volume, fan fiction about the rapper, if you’re curious.</p><p>As we explored the number of story categories and forums within Wattpad we found prolific communities sharing the wildest parts of their minds through stories. By far the biggest success within fan fiction (and informal publishing) is 50 Shades of Grey, which <a href="https://en.wikipedia.org/wiki/Fifty_Shades_of_Grey#Background">started as Twilight fan fiction</a>.</p><p>So we began thinking about the web and its impact on publishing. Traditionally, the final product would be a book in the local store, but what <em>is</em> the “final product” when the process to publishing is just a ≤button/&gt; on a page?</p><h3>The End of a Story is No Longer Static</h3><p>Traditionally a book would go through a publisher’s Book Product™ machine — but the web now allows the final product to be something different. The final product for an online book is no longer a function of traditional publishing’s Book Product™ formula, but something much less refined. A novella can be quickly written and published, and then evolve with reader interest to spawn a whole series of stories.</p><p>As we began to work with Wattpad’s API, we took a closer look at the niches that existed within the story comments and forums on Wattpad. We saw authors discussing ideas, and adding thoughts in hopes of pushing each other to create new narratives. This public process means that the end product isn’t static <em>thing</em> — and because the web allows a story to be edited and rewritten, every story has the ability to be dynamic and changing. Stories may end, but the process for many books is always evolving — which is especially true on Wattpad.</p><h3>CODEX Hackathon on Twitter</h3><p>Ambient lighting. Gives @pippinlee a nice glow. He worked on Forkpad with Max. pic.twitter.com/ODK8B9ntdo</p><h3>Can Remixing Help the Writing Process?</h3><p>From our quick study of Wattpad, Max and I realized that this community could likely use a tool to help create a better feedback loop for authors working through story ideas. The idea of the “remix loop”, where creators spin off each others work can be incredible powerful tools within the writing process. Forkpad allows writers to take a part (“chapter”) from a Wattpad story and adapt it to their own liking.</p><p>When developing Forkpad, we found the concept of being able to change an ending or adapt characters to follow our own ideas a fun and important tool in the writing process. The ability to “fork” a Wattpad story means that others can post a link to their Forkpad version back on Wattpad to better share their thoughts on a story, as well as build off of each others’ work.</p><p>This idea of “forking” code is now common in software development. When computers were giant room-sized machines, the people who operated them (usually academics) would use tape as a medium to “write” their programs on. They would then feed these lengths of tape into a reader which would interpret their programs and run them on the computer. The programs were usually relatively small because computers could only process small bits of information. The idea of open source can be traced back to these early computer users, who stored their tapes in a drawer so that anyone using the computer could use their completed code. This saved colleagues from having to write a similar program from scratch, because they could share their completed tape programs.</p><p>Despite a period of highly commercialized and proprietary software during the 1980s and 1990s (a shift catalyzed, in part, <a href="https://en.wikipedia.org/wiki/Open_Letter_to_Hobbyists">by Microsoft</a>), developers’ natural desire to share their code has roared back to life in the last twenty years (embodied by <a href="https://en.wikipedia.org/wiki/Linus_Torvalds">Linus Torvalds</a> and his software versioning system <a href="https://en.wikipedia.org/wiki/Git_(software)">Git</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFy69Cx6aidKv8BrMit7VA.png" /><figcaption>Early computers would run programs that were created by punching holes in tape. Photo: wikimedia</figcaption></figure><p>Building off each other’s work is common in the open source world of software, where a team may spend a year solving a specific problem, and then they’ll share the code with other developers so that others don’t have to waste their time solving a problem that’s already been solved. Starting with an empty text box is a barrier to writing — so we wanted Forkpad to help get writers writing more. The process of consuming other’s work, and building off of it is one way that we can learn to be better writers, and Forkpad aims to make that easier.</p><p>As Saturday ended and Sunday began, we’d already built the main functionality of the Forkpad app — so we spent the last few hours before demo time getting our app up and running with a database so that writers could get a link that they could share. The ability to easily share their remixes means writers will hopefully be encouraged to build off each others work.</p><p>The process for using and publishing with Forkpad is much less formal than a traditional publishing process, but we think giving writers the ability to <em>get writing </em>will always trump a process that start with big end goals in mind. Writing is a process, so hopefully Forkpad can ask how that process can evolve for writers with the help of the machine. Much like the atmosphere at CODEX, it’s not a zero-sum game between the machine and publisher, but finding situations that allow both to be part of the creative process.</p><p>We’re not sure what writers will make, and we definitely don’t know what the end products will be, but we think it will be something fun.</p><p><a href="http://forkpad.me/">Forkpad.me</a> is live. Send us some Drake fanfic?</p><p>@<a href="https://twitter.com/maxbittker">maxbittker</a> and @<a href="https://twitter.com/pippinlee">pippinlee</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49f2a6900ca9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/will-the-future-of-writing-be-more-like-software-49f2a6900ca9">Thoughts from making tools for literature</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Terror and Hope of CODEX Hackathon]]></title>
            <link>https://medium.com/codex-hack/the-terror-and-hope-of-codex-hackathon-35952750fbc6?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/35952750fbc6</guid>
            <category><![CDATA[codexhack]]></category>
            <category><![CDATA[literature]]></category>
            <category><![CDATA[publishing]]></category>
            <dc:creator><![CDATA[James Carmichael]]></dc:creator>
            <pubDate>Fri, 10 Jul 2015 01:40:27 GMT</pubDate>
            <atom:updated>2015-07-10T03:17:22.714Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Og0azBTL9K1zIgskX-NJ8w.jpeg" /></figure><p>I’m a writer. As I type this, I’m angry — seethingly, deeply angry; the kind of angry that leaves me cursing at myself during trail runs that are meant to relax me, because my mind races off, tears down trails of its own. Why so angry? Because I can’t figure out a plot point for the next installment of my serialized novel, <a href="http://www.amazon.com/Erras-Throne-Column-Tablet-Book-ebook/dp/B00LCSRS6I/ref=sr_1_1?ie=UTF8&amp;qid=1436480474&amp;sr=8-1&amp;keywords=erra%27s+throne">Erra’s Throne</a>; the fifth section was supposed to be out <em>weeks</em> ago and it’s not, because I am a broken failure of a man who deserves to be self-cursed whilst running the mountains. I could write something, sure; “get it out there”. Easy. But this thing, it’s my heart. It’s not meant to be <em>some</em>thing; it’s meant to be, for at least a few readers, at least a couple: <em>everything. </em>That’s what it is for me. So I care enough about this dumb plot mechanic, that probably no one will notice, in this serialized novel that may never be read by more than a couple thousand people, to strip myself down to a spare raging core till I find the right words to make this story at least close to what I know it can be.</p><p>I’m telling you this here, before sharing my personal impressions of a weekend spent with some coders in San Francisco, to juxtapose it with this next thing:</p><p>I don’t give a shit about books.</p><p>The “CODEX” part of the <a href="http://codexhackathon.com/">CODEX Hackathon</a>, the San Fran event at which I met all these coders (and designers, and other people with skill sets I do not understand), refers to what you and I’d just call a “BOOK”. Meaning physical object; meaning pieces of paper bound together between thicker, harder pieces of (probably) paper, with a spine, and et cetera. The longevity, durability, and revolutionary impact of this technology “cannot be overstated,” and I’m sure as heck not going to rehash it here. At the hack (I’m just going to make up shorthand names for this event. I didn’t even know a “hackathon” was a thing, before this weekend), I was fascinated by how many techies proclaimed a heartfelt, visceral connection to <em>physical</em> books. They waxed about all the usual stuff: smells, textures; the grain of paper on your hands; the weight-memory of a familiar volume; annotations from a younger self, annotations from the friend from whom you borrowed this book <em>oops, </em>what, like: twenty years ago?</p><p>And yes, sure: I’ve got some old books that I care about. I’m not here to poop on anyone’s sensual pleasure.</p><p>But also, seriously: I could not care less. About any of that. About “books”, as a physical technology. The vestigial is accidental, vestigial, a <em>format.</em> I couldn’t care less.</p><p>And I kind of think you shouldn’t, either.</p><p>Now that I’m an expert hackathonian, I have the credibility to say things like: <strong><em>technology’s changed everything</em></strong>. No, but seriously. No one has to lug books around (well, most kinds of books); personal and professional libraries can be accessed anywhere, all the time; a lifetime of reading no longer carries unacceptable physical burdens: homes given over to codices, to pulp and glue stacked in shelves and on every available surface; we can imagine a day when trees are not asked to yield up their flesh that we may pass learnings and fictions between ourselves; those annotations we cherish are kept in a cloud where, despite what our chestnut-sized lizardbrains think, yeah probably they’re safer than they’d be in that charmingly dog-eared copy of <em>The Three Musketeers</em> that we read on the subway in 10th grade.</p><p>With all this in mind, I was <em>psyched </em>for CODEX Hackathon. <strong><em>“What’s the Future of Reading?”</em></strong> Darn straight. And it’s a good thing I was psyched, and a good thing I already had all that in mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6wsCxtcbr8ld_dFOqUW8w.jpeg" /></figure><p>Because even thus prepared, the whole thing messed with my head something wicked.</p><p>This was the hackaroo, in a nutshell: teams made up of designers, developers, and a handful of people like me got together. Each team tackled some question facing reading in this, our increasingly digital age. The deliverable each team created was a prototype — an app or a tool — that somehow addressed contributed to <em>the future of reading.</em> For an excellent summary of some of what was created, check out this <a href="https://medium.com/codex-hack/hacking-the-future-of-publishing-3127764cbde">recap</a>. For my project, I was paired with <a href="https://www.linkedin.com/in/michaelbernstein">Michael Bernstein</a>, a terrific “full stack” (not pancakes) developer, to create a fun and easy tool for selling literary serialized fiction. We made <a href="https://dickensbyemail.myshopify.com/">this</a>, and I think we’ll build on it — Michael was awesome; is awesome. Hire him, reader.</p><p>Throughout the weekend, as I was talking to these designers and programmers about stories and how we receive them; and at the <em>end</em> of the weekend, watching the presentations, the thing that struck me over and over and over was the extent to which technology is changing <strong><em>every</em></strong>thing in this game. This is about much more than than a shift from physical books to, whatever, Kindles and smartphones. Or rather, that shift is about much more than whether you have paper or silicon in your hand as you read. Just as the physical book, and the printing press, and all of the technologies that defined publishing for the last couple centuries are about much more than ink, paper, and glue. They’re about magazines and the cultural tropes that model gave rise to; they’re about “news” “papers” and what that did to how we experience the wider world; they’re about the <em>existence</em> of the novel, #ffs, which to be honest when I say the word “writing” is pretty much the thing that I’m thinking about 96 percent of the time.</p><p>And that, <em>all of that, </em>is what’s going to, has to, change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*9CJAZzgCafaAEeB1niuNaw.jpeg" /></figure><p>Representatives from <a href="https://www.wattpad.com/signup">Wattpad</a> (“Discover a world of unlimited stories”) and <a href="https://jukepop.com/">JukePop</a> were at the hackathon. These platforms — including one called I think <a href="https://medium.com/">Medium</a>, of which maybe you’ve heard ?— allow anyone to write and distribute fiction, non-fiction, essays, whatever. JukePop is working to create tools to help writers multimedia-ize and splash up their prose; there in the hackazone, several of the prototypes developed were about using digital tools to enrich the reading experience with cartography, sounds, and social connections.</p><p>But the change all this tokens is still deeper than that. Anyone, anyone can now write and be read. In some cases, can be read by <em>lots </em>of enthusiastic people. And what’s interesting is that, right now, I’d say, looking across these platforms and at self-published work, taking in this whole democratized open ecosystem: a lot of it is just total garbage. Sez me. Does that matter? I mean, really: does it matter that I think that, at all?</p><p>Nope!</p><p>Not just because that’s one opinion, mine, on a subjective matter; and further I’m just some weird guy who lives with 2 cats and makes not so much money with apparently-so-good-I-can’t-think-of-the-next-bit fiction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Kj2kvt3UtmmULUfbPMz1EQ.jpeg" /><figcaption>Me eating Malaysian food at the CODEX Hackathon. They feed you a scary amount at these things. It is great.</figcaption></figure><p>Not just that. My whole framework, and the framework of everyone like me; the aesthetics against which these bright new ideas at the hackathon kept colliding: they’re all built into me by the <em>past</em> — by <em>books</em>, <em>physical </em>books, by all the commercial and artistic and cultural forms that evolved around glue pulp and ink. And this hodgepodge of experimentation — go, check out the <a href="https://hackdash.org/dashboards/codex2015">hackathon’s projects</a>, see what I mean —this is future. Even if I hate it. I don’t matter. You don’t, either; neither does your or my ineffable, irrefutable, true-in-the-deepest-place-of-ourselves sense of beauty or wonder.</p><p>There’s a rude — in the good sense — robustness to this truth. It’s bracing, regenerative, literally literarily revitalizing. Reading is dead. Long live reading; everything’s new here on out. Stories, writing, prose — anything that engages the interface of human and text — is changing, totally. And what was exciting and frightening at this hackathon, for me, was being dropped amongst humans for whom this kind of evolutionary shift is automatic: coder- and developer-types, for whom the tumbling forward progression of technology and markets is an everyday fact.</p><p>I’m a writer. I look backwards by disposition; I settle wait and see until something forms, around which I can build shape; or I look inside, at the precious little jewel-box of the thing I’m making up, trying to find the exact right f***ing plot-point that will allow me to get on with my life.</p><p>What has to happen if I want to continue to exist as a writer, though, is I have to adapt. Because these Big Changes are not “coming.” They’re here. They’re happening. Really, check out the <a href="https://hackdash.org/dashboards/codex2015">Hackathon’s projects</a>. They’re zygotic; they are funny; they’re strange.</p><p>They are true.</p><p>This is what now is, and if you care about stories — if you’ll tear yourself apart for weeks, searching out a perfect plot point; if you can’t help but see some kind of moral deficiency in prose that (you think) is lousy; if you’re someone who enjoys reading those sentences and that plot point, and thinking: “yeah. pretty good.” — you have to care about this. You don’t have a choice. What a gift, to be forced to respond to upheavals, as we move forward together towards something terrifying, exciting, and new.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35952750fbc6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/the-terror-and-hope-of-codex-hackathon-35952750fbc6">The Terror and Hope of CODEX Hackathon</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking the Future of Publishing]]></title>
            <link>https://medium.com/codex-hack/hacking-the-future-of-publishing-3127764cbde?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/3127764cbde</guid>
            <category><![CDATA[codexhack]]></category>
            <category><![CDATA[literature]]></category>
            <category><![CDATA[publishing]]></category>
            <dc:creator><![CDATA[Anika Gupta]]></dc:creator>
            <pubDate>Thu, 09 Jul 2015 17:35:55 GMT</pubDate>
            <atom:updated>2015-07-09T17:35:55.411Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KCPOqNj2ChMtdk_sI11Z2A.jpeg" /></figure><p>For someone who has grown up with reading, the idea of “reinventing” the reading experience might seem either like sacrilege or like a waste of time. At the <a href="http://codexhackathon.com/"><strong>CODEX Hackathon</strong></a>, which ran from June 26–28 in San Francisco, several of us spent the first few minutes of the event rhapsodizing about the physical joys of reading: trailing fingers over unbroken spines, inhaling the rich and varied scents of different papers. To those who read, the book is no trifling matter, and its form is as much a part of its purpose as its content.</p><p>And yet, with or without our consent and awareness, the experience of reading is changing under us, and that is part of what this hackathon was meant to address. Newspapers, as has been much noted, have migrated online, but perhaps they were a lagging indicator. The experience of finding and securing information has become a rapid and ideally lossless process. There is something deeply inefficient (and I’m not just talking about time) about finding a book, reading it, taking notes out of it, tracking the notes back to some imaginary writer’s attic, and consulting them as a primary or even secondary sources.</p><p>If research has the whiff of necessity about it, how do we address the notion of pleasure? Some 69 per cent of Americans <a href="http://www.pewresearch.org/fact-tank/2014/01/24/10-facts-about-americans-and-public-libraries/"><strong>read a print book</strong></a> in 2013, and another 55 percent <a href="http://libraries.pewinternet.org/2013/12/11/libraries-in-communities/"><strong>disagree</strong></a> that libraries have not kept up with new technology. So what are the pleasures of reading in the digital age?</p><p>For some people reading is a social experience, and the Internet has enabled a greater breadth of connection. At one point, Goodreads was one of the country’s fastest-growing <a href="http://www.theatlantic.com/entertainment/archive/2014/02/millions-of-people-reading-alone-together-the-rise-of-goodreads/283662/"><strong>social networks</strong></a>. During the two days of the CODEX Hackathon, one group decided to create an app that would help people read more, and so their members interviewed the rest of us about the greatest obstacle to our reading.</p><p>“What keeps you from reading more books?” asked one of the developers from this group. He’d come over to a corner of the <a href="http://codeforamerica.org/">Code for America</a> basement in SF, where my group (there were four of us) were reclining while debating our own ideas. “Is it that reading is a lonely experience?”</p><p>The rest of us exchanged looks of astonishment. The idea that anyone could perceive reading as lonely had never occurred to me. Anyone who has “lent a friend a book” understands what it means to exchange a unique intimacy. <em>Here,</em>the action suggests, <em>learn about me by learning what has moved me.</em></p><p>That group <a href="https://medium.com/codex-hack/introducing-streaq-one-chapter-a-day-33a70a869cb8">eventually went for another idea</a>, but they weren’t entirely wrong: reading isn’t lonely, of course, but it’s precisely that absence of loneliness that might pave the way to other, equally close, connections.</p><p>The hackathon attendees being a group of (largely) millennials, one hackathon team evolved the notion of “<a href="https://hackdash.org/projects/558f188edb0166dd1b11da53"><strong>Kindlr</strong></a>” — a dating app for people who’d rather be reading. A company called BitLit Media has released an app called “<a href="http://www.bitlit.com/"><strong>Shelfie</strong></a>,” which allows users to take photos of the books on their bookshelf. The app then matches the user with free or low-priced ebook versions of those same print books. There’s something very nifty about Shelfie’s app, and the Kindlr group used Shelfie’s API to allow potential daters to upload pictures of their bookshelves as the ultimate guide to their psyche. While giving his three-minute demo at the end of the hackathon, the presenter (charming, dry) offered a series of questions on which the app would match potential couples: “What is one book you would never read?” Or, more tellingly, “What is the last book you lied about finishing?” (Not mentioned: “Is it wrong to lie about finishing?”)</p><p>Of all the hackathon ideas, this one got some of the biggest laughs, and possibly also some of the most appreciative glances. Maybe it’s a bad idea to look to readers as models of fidelity: any true reader knows that choosing a “favorite” book is an exercise for noobs, because one of the greatest pleasures of reading is its near-infinite variety. Even the Kindlr presenter acknowledged the pointlessness of “The One”, saying of a potential profile match who had only 10 books in her digital library, “I’m not going to date a filthy casual.”</p><p>In keeping with the theme of unlikely matches, another crowd favorite was “<a href="http://neuralpubliclibrary.com/"><strong>Neural Public Library</strong></a>” — a team that described their concept as “a library of book titles and authors generated by a recursive neural network.” The fictional titles are generated by the network, while the cover images are grabbed from Flickr. Although a “recursive neural network” sounds only slightly more complex than the Dewey Decimal System, NPL’s website (and accompanying Twitter <a href="https://twitter.com/neurallibrary"><strong>stream</strong></a>!) serve a host of humorous auto-generalia. Today, in the Romance genre, this is what their website gave me:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QJDC-iVL4gBjMlMtOFPPGQ.jpeg" /></figure><p>Speaking of the challenges of finishing, more than one group tried to shorten the physical experience of reading. “<a href="https://hidden-plateau-7201.herokuapp.com/"><strong>Instant Classic</strong></a>” was developed by Media Lab alum <a href="http://slifty.com/">Dan Schultz</a> and his team. Their program shortens any text by removing words and sometimes whole sentences. Users can choose the percentage of shortening they require. So, for example, the immortal lines:</p><blockquote>“To Sherlock Holmes she is always <em>the</em> woman. I have seldom heard him mention her under any other name. In his eyes she eclipses and predominates the whole of her sex. It was not that he felt any emotion akin to love for Irene Adler. All emotions, and that one particularly, were abhorrent to his cold, precise but admirably balanced mind.”</blockquote><p>Become the following, when shortened to 50 per cent:</p><blockquote>“To Sherlock Holmes, she is always <em>the</em> woman. In his eyes she eclipses and predominates the whole of her sex. It was not that he felt any emotion akin to love for Irene Adler, since all emotions, and that one particularly, were abhorrent to his cold, precise but admirably balanced mind.”</blockquote><p>By reducing to 10 per cent, we get:</p><blockquote>“To Sherlock Holmes, she is always <em>the</em> woman, not because of any emotion akin to love.”</blockquote><p>What a fascinating transition, and not a wholly nightmarish paraphrase. Maybe Holmes, with his penchant for directness, would approve. In his presentation, Schultz acknowledged that this function may not be the best thing for fiction, where the pleasure lies in more than effective movement from Point A to Point B. But then again, doesn’t everyone kind of agree that Dickens and Hugo could have used some forced-shortening? Of course, set the browser’s view preference to 0 per cent and the text disappears altogether. A great piece of performance art, maybe, but anxiety-inducing if permanence is what you crave.</p><p>Another fascinating entry in the “read faster” Olympics was “<a href="http://boustro.com/app/"><strong>Boustrophedon</strong></a>,” the practice of reading alternating lines of text in opposing directions. Here are the first few lines of “A Room of One’s Own”, rendered in Boustrophedon’s reader:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QvCH2NqNg3kTHgp5mWxgJg.jpeg" /></figure><p>According to the project’s creator, “The ancient Greeks and Romans did it!” I leave it to you, dear reader, to decide whether this method of reading feels easier.</p><p>Mailchimp contributed an API as well as a prize for the best team that used it: Apple watches, or Android equivalents. Several teams, striving for this trophy, experimented with serialized fiction, an art form that had its heyday in the Victorian Era (astonishing as it may now seem to both industries, fiction once sold magazines). And yet, if serial fiction relies upon the interplay of frustration and longing, then certain authors are already experts at tugging the strings. Or, as one of my friends said in response to the <a href="https://hackdash.org/projects/55906df0db0166dd1b11da87"><strong>MailBook</strong></a> project: “Can we make something like that for George RR Martin?”</p><p>There were many more projects, and a full set of these projects resides <a href="https://hackdash.org/dashboards/codex2015"><strong>here</strong></a> (with demos, if you’re so inclined!) My own group began with the goal of creating an “immersive” reader for an e-text, thereby transmitting the sensory experience of literary place. After two days of hacking and hawing, we had a workable demo of Chapter Five of Sir Arthur Conan Doyle’s “Hound of the Baskervilles.” As a reader scrolled through, a map in the background switched locations, showed images, and even played sound effects. A snapshot from our final presentation, below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ieT8hiw4pNxga_xcgq9v_g.jpeg" /></figure><p>As with all such endeavors, the joy lay not just in releasing a prototype, but in working alongside a group of like-minded individuals. My teammate Eric Gardner, the Digital Publications Developer at the <a href="https://www.getty.edu/museum/">J. Paul Getty Museum</a> in Los Angeles, introduced me to <a href="http://jekyllrb.com/"><strong>Jekyll</strong></a>, <a href="http://madebymany.github.io/sir-trevor-js/"><strong>Sir Trevor</strong></a> and <a href="https://www.mapbox.com/mapbox-studio/#win64"><strong>Mapbox Studio</strong></a>, all through the simple mechanism of using them while I happened to be looking over his shoulder. Teammate <a href="http://twitter.com/edwardbenson">Ted Benson</a>, who describes himself on his website as an “expatriate of MIT CSAIL”, lent us a hand with the spreadsheet-based website management he’s been developing over at <a href="http://www.cloudstitch.com/"><strong>Cloudstitch</strong></a>. My final teammate, Arendse Lund, was a writer-in-residence in Colorado.</p><p>These relationships were the point, not the byproduct. <a href="https://twitter.com/jenny8lee"><strong>Jennifer 8. Lee</strong></a>, who curated the crowd as well as the spectacular food (most of the items I didn’t recognize, and I’m not an inexperienced eater), had the following to say about her motivations: “The most important mission of the CODEX Hackathon was building relationships through face-to-face interaction, since publishing is an industry that relies so much on personal trust and it’s an industry that has to move forward as an ecosystem.” (Lee is CEO of the <a href="http://plympton.com/"><strong>Plympton</strong></a> literary studio, who count the <a href="http://twitterfictionfestival.com/">Twitter Fiction Festival</a> among their projects.)</p><p>At the hackathon, the best projects didn’t reinvent the reading experience so much as build scaffolding around it. The experience of reading is never face-to-face, which is both its allure and its challenge. In this, reading may be a great correlate for something like Facebook: it flirts heavily with human connection, but at the end, commitment remains uncertain. A great book-based app, then, has to bring the outside world right up to the gate of the word, and then, without fanfare, abandon it.</p><p>The next CODEX Hackathon takes place in Boston/Cambridge from January 8–10, 2016. Save the date.</p><p><em>Anika Gupta is a graduate student in Comparative Media Studies at MIT. This post first appeared on the CMS </em><a href="http://cmsw.mit.edu/hacking-the-future-of-publishing/"><em>blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3127764cbde" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/hacking-the-future-of-publishing-3127764cbde">Hacking the Future of Publishing</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Demystification of Silicon Valley]]></title>
            <link>https://medium.com/codex-hack/the-demystification-of-silicon-valley-b2016eea1280?source=rss----3a818604ad72---4</link>
            <guid isPermaLink="false">https://medium.com/p/b2016eea1280</guid>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[silicon-valley]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Peter Siemens]]></dc:creator>
            <pubDate>Wed, 08 Jul 2015 18:12:21 GMT</pubDate>
            <atom:updated>2015-07-08T21:35:56.549Z</atom:updated>
            <content:encoded><![CDATA[<h4>How a Literary Hackathon Reset my Distorted Perception of the World’s Technology Epicentre</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*83MQBu0IyOR0ohkGmlRSBg.jpeg" /><figcaption>Three tired hackers standing on the rooftop of a SoMa apartment building. Photo: Pippin Lee</figcaption></figure><p>I’m from Saskatoon, Saskatchewan, a small city on the Canadian prairies with a disproportionately high F-150-to-human ratio. Most people can’t spell it or <a href="https://www.youtube.com/watch?v=qWCS7k1TgME">pronounce it </a>— much less find it <a href="https://www.google.ca/maps/place/Saskatoon,+SK/@52.6019719,-106.2406302,5.11z/data=!4m2!3m1!1s0x5304f6bf47ed992b:0x5049e3295772690">on a map</a>. I left after high school to study computer science at the University of British Columbia in Vancouver, but I’m back home this summer to spend time with friends and family.</p><p>I’m like a lot of other young programmers. I’m ambitious and overly confident, with dreams of leaving school, creating the next Facebook and moving to Silicon Valley. As a teen, my favourite superhero movies were <em>The Dark Knight</em> and <em>The Social Network. </em>I used to follow every new startup and obsess over which schools had the best computer science programs — all in preparation to one day make it to the big leagues. As a young kid from rural Canada, I viewed Silicon Valley as a place where genius Stanford and Harvard dropouts gathered to transform venture capital money into world-shaping products through some mysterious alchemy.</p><p>But through my obsession, I effectively created a place that, for the most part, only existed inside my head. I had never spent any time there or even talked to other people who had. Everything I thought I knew was conjured through Hollywood movies, <em>Wired</em> articles and other tech folklore, and because of this, Silicon Valley was always a world that felt impossibly far away.</p><h4>My Journey to the Valley</h4><p>While working as the web developer at the <a href="http://ubyssey.ca/">student newspaper</a> this year, I wrote code for interactive and data journalism projects, most of which I shared online. People began to notice and I made a few well-connected friends, including <a href="https://medium.com/@pippinlee">Pippin Lee</a>, another student involved with a community of journo-coders known as <a href="http://hackshackers.com/">Hacks/Hackers</a>. In mid-June he told me that I might be able to receive a travel stipend to fly to San Francisco and attend the <a href="http://codexhackathon.com/">CODEX Hackathon</a> — a three-day event that was part of this year’s annual American Library Association conference.</p><p>Intrigued, I went to the website and spent 10 minutes filling out <a href="https://plympton.submittable.com/submit/42415">the application form</a> before I hit submit.</p><p>Literally, a few moments later, I received a terse email from a hackathon organizer that read something along the lines of “price out your travel expenses and we’ll go from there.” If I were Charlie, that email was my Golden Ticket. Within minutes I had secured a free round-trip flight and accommodations for the weekend. It all happened so fast. I was on my way to my Disneyland.</p><p>The goal of CODEX was to put engineers and literary folk in the same room and see what they could build together. Although my experience in a college newsroom somewhat qualified me as a “literary hacker,” I was still overwhelmed when I was asked to attend. I had never been to a real hackathon before, let alone one in the very place I had been dreaming of visiting for so many years. As it turns out, that place is only a three-hour plane ride away from my isolated prairie town.</p><p>I wasn’t sure what to expect from the event. Most hackathons I hear about consist of ultra-lucrative cash prizes that attract hungry, hardcore teams of programmers who stay up all night building outrageous pieces of software and hardware. I was worried that I might not have what it takes to participate in this kind of event, but my friend assured me that a literary-themed hackathon probably wouldn’t be <em>that </em>hardcore.</p><p>CODEX was held at the <a href="http://codeforamerica.org/">Code for America</a> office in the SoMa district of San Francisco, right near some of the world’s most recognizable tech companies (Twitter’s headquarters is just two blocks away). CfA was like a tech office venue from a Hollywood movie set; the building is designed around a large open space with plenty of couches, worktables, whiteboards and project rooms for hackers to utilize. The fully stocked kitchen and beer-on-tap solidified its status as programmer heaven.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GPtPgl65gU84aU6jWq8YOw.jpeg" /><figcaption>Photo: Jennifer 8. Lee.</figcaption></figure><p>At the start of the first day I sat down with the other Canadians I knew (including my friend and teammate Ben, who had also received a Golden Ticket) at a table in the corner of the room. There was a man across from me who (I later learned) is a software engineer at Google. But in that instance he was just another coder. In fact, as I began to learn more about the people around me — some were students from Harvard, one worked at Twitter, another at Dropbox — I began to realize that I was surrounded by extremely talented individuals. The kind of people I aspired to be as a teenager.</p><p>But the most surprising thing about it? They were totally normal.</p><p>The hackathon officially began and we worked feverishly on our apps for the next 36 hours. Immediately I was amazed by how much fun I was having. Programming is something I often do alone in my bedroom, and being in a place where people had gathered to drink beer and write code made it that much more enjoyable. I had no problem feeling at home amongst the gentle hum of keyboards clicking, laughter, and friendly chatter.</p><p>Ben and I teamed up to create an app that would use the <a href="http://kb.mailchimp.com/api/article/api-3-overview">new MailChimp API</a> to re-think email newsletters. We wanted to harness the traditional model of an email blast and use it as a way to collect “everyday stories from everyday people” that were somehow linked to a larger theme, an idea inspired by <a href="http://storycorps.org/">StoryCorps</a>. Users would receive writing prompts from subscribed lists in their inboxes, and then respond by replying to the emails. Responses would be gathered and showcased on the website, where other users could leave feedback and vote for the responses they liked best.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*thG12WQRVvCTpoUa6Jo8Bg.jpeg" /><figcaption>CODEX attendees gather for project presentations and demos. Photo: Jennifer 8. Lee.</figcaption></figure><p>But our demo was a disaster. The fancy livestream feature we had built failed to function, and it was as embarrassing as it was frustrating; we had spent the weekend building something cool, only to have it fail when we needed it most. For a few minutes I felt like the organizers had made a mistake in bringing <em>me </em>to the hackathon. “They should have invited somebody who could actually build something,” I thought.</p><p>Luckily I was able to redeem myself by doing a few one-on-one demos once we got the app working again. The problem during the live-demo was that the volume of responses from the audience clogged up the system. Lesson learned: load testing before a live run is important.</p><p>Others liked what we had built, and I was able leave that night without any lingering shame. I had just participated in my first hackathon, I had a lot of fun, I met a lot of people, and my app didn’t totally suck.</p><h4>It’s a Different World</h4><p>I spent the rest of the night with friends from the hackathon — some new, some old — at a trendy loft apartment just down the street from Code for America. It belonged to <a href="https://medium.com/@jenny8lee">Jennifer 8. Lee</a>, the mastermind behind CODEX, as well as the founder of <a href="http://plympton.com/">Plympton</a> — a literary studio focused on digital innovation publishing. Put simply, she’s <a href="https://en.wikipedia.org/wiki/Jennifer_8._Lee">a big deal</a> in the publishing and technology world. And there we were, four twenty-year-old university students sitting on her white sofa eating potato chips and hummus while reflecting on the weekend.</p><p>That’s when it began to hit me. I had just flown half-way across the continent to participate in a programming event in the Hollywood of the tech industry, not because I had attended an Ivy League university or created a killer app, but because I had simply demonstrated a passion that others also shared.</p><p>I had started my CODEX weekend with the opening Friday reception at the <a href="http://www.businessinsider.com/github-office-tour-2012-8">remarkable GitHub headquarters</a>. Near their full-scale replica of the Oval Office, I mingled with other hackathon attendees and industry professionals, all of whom were incredibly friendly — which for some reason took me by surprise.</p><p>I had expected a culture of eliteness and stunning intellect — a cropping of people who didn’t feel the need to chat with a young Canadian student who, compared to them, knew very little. But after speaking with several people — one who went from telling me about his Nvidia robotics engineering work to giving me advice about which local bars I should hit up — I was proven wrong. Nobody cared about which school I went to or where I worked; it was a party, and they were there to have fun.</p><p>The truth is that I expected these people to judge me by my resumé because that’s how I was judging them. In my ignorance, I was sizing people up as part of the artificial Silicon Valley I had constructed in my mind. When I realized they were just people who also <em>really</em> liked computers (just like me), I began to feel less intimidated.</p><p>The tech culture I had imagined was not the one I experienced that weekend; I anticipated a world that would spit me out as soon as I arrived, but instead it was overwhelmingly welcoming.</p><p>I brought that new mindset with me when I went to have lunch at Twitter with someone I had met at CODEX later that week. Between sips of kombucha (which they have on tap in one of the three cafeterias we visited), I looked around with a fresh set of eyes. Sure, the Twitter offices were just as glamorous as I had imagined, but the people who inhabited them were just like anybody else I had met. I even passed Jack Dorsey on the street outside, and if it weren’t for the fact that I’ve seen him on numerous magazine covers, I would have had no idea who he was. He just looked like an ordinary person having an ordinary day. (He has trimmed down <a href="http://money.cnn.com/2015/06/12/news/companies/jack-dorsey-twitter-beard/">his beard</a>).</p><p>Maybe it’s just me. Perhaps my naiveté was unique, and the mirage I created is one that few can relate to. But I like to think that it isn’t. I don’t think I’m the only one who has crafted false expectations from childhood aspirations. In my mind I viewed Silicon Valley as some kind of exclusive club, but after seeing the real thing, it now feels far more accessible. I believe that this shift in thinking — from distorted perception to refreshing reality — could be shared by the other aspiring engineers, entrepreneurs, and hackers who imagine themselves one day starring in their own Silicon Valley superhero movie.</p><p>I’m not saying I’ve made it, and maybe I never will. All I’m saying is that Silicon Valley isn’t just a place for the pre-ordained elite — it’s a place where smart, hardworking, ordinary people gather to drive innovation. And it’s not as far away as I had imagined.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2016eea1280" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex-hack/the-demystification-of-silicon-valley-b2016eea1280">The Demystification of Silicon Valley</a> was originally published in <a href="https://medium.com/codex-hack">CODEX HACK</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>