Your body and mind aren’t designed to work for 24 hours straight. Yet the architecture of a hackathon is designed to force you to do just that — code for 24 hours nonstop. How can you deliver quality code quickly under those conditions?
At the 2012 TechCrunch Disrupt Hackathon in San Francisco, we asked attendees (most seasoned hackathoners) how they do it. Here are their answers:
The views expressed on this blog are those of the author and do not necessarily reflect the views of New Relic. Any solutions offered by the author are environment-specific and not part of the commercial solutions or support offered by New Relic. Please join us exclusively at the Explorer’s Hub (discuss.newrelic.com) for questions and support related to this blog post. This blog may contain links to content on third-party sites. By providing such links, New Relic does not adopt, guarantee, approve or endorse the information, views or products available on such sites.
Interested in writing for New Relic Blog? Send us a pitch!