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: