Blair Arch, Princeton University

Why a Code@Night is not a Hackathon

Blair Arch, Princeton University

Why a Code@Night is not a Hackathon

I’ve written in the past about what a Code@Night is. And they’re wonderful. One of my favorite topics, really. People come to these things and they just code all night. Great experience. Tons of fun. Fruit. PacMan. Yadda, yadda, yadda.

I tell people this all the time, and a pretty common response is “so, it’s like a hackathon?”

So I think for a bit. There’s coding. There’s minimal sleeping. There are tech talks. There are pizzas, snacks, and refreshments. Fruit is hard to come by at a hackathon, but it can be there too. So I concede, “yeah, it’s a bit like a hackathon.”

But I know we’re wrong. Code@Night doesn’t feel like a hackathon at all.

Here, I made you an analogy. It’s not a good one, but you can read it anyway. “A hackathon is to a Code@Night as a track race is to a stroll through a park.”

Or for you symbolically minded folks…

Hackathon : Code@Night :: Track race : Evening stroll

How can they feel so different when the only core difference is that we’ve removed the competitive aspect?

Well, in some ways Code@Night is a lot like a hackathon, but in others it’s not at all. It’s a hackathon minus the competition, plus the assortment of non-hackathon things that happen at Code@Nights. e.g. Pacman, the occasional contest, the tight-knit community, lots of fruit, a tech talk smack in the middle. Also, Code@Night runs for 12 hours in the worst case (if people stay for breakfast, we’ll feed them), but more realistically only goes from 9 pm to 3-4 am. A hackathon usually lasts 24 hours or more.

It sounds like these are small differences from a hackathon, but it’s really a completely different atmosphere. There’s no start and end time for your project. You can work on the same thing Code@Night to Code@Night if you want. And people don’t cluster into teams the way they do at hackathons. You also end up getting large group discussions going, which you rarely get at hackathons because people are rushed to work on their 24 hour product. No one’s worrying about prizes or judges. You don’t have to demo anything to feel accomplished (but we love demos! they’re sure encouraged!) You can build what you want to build, not the thing you think will win over an audience.

Code@Night isn’t about starting. It isn’t about finishing. It’s about doing. It’s about learning. It’s about being a part of a community. By removing the artificial competitive aspects and time constraints that hackathons impose on coding, we’re left with a really rewarding experience. People step back from their coding in ways they don’t at hackathons. They teach about Python, about Hadoop. They sit in boxes ( or put boxes on their heads). They share their projects. They debate bacterial growth characteristics on the surface of crisp orange-colored, peanut butter-flavored flakiness coated in compound chocolate. They talk about technology. And sometimes they write poetry.

So, the next time someone asks if a Code@Night is like a hackathon, I’ll be ready with my “kinda, but not really, actually no” answer. And I’ll be ready to say how they’re different, and how I actually prefer the Code@Night. But hey, I’m biased, I organize the things.

Next Code@Night? It’s Sept 13, 9 pm. Sherrerd, Third Floor. Open to all Princetonites. Hope to see you there!

Discussion 💬