If you use that much Red Bull, you got 2 issues (at least): the sugar gives a rush, but the bloodsugar level will plunge. And each time you continue it plunges even harder and faster.<p>Second, Red Bull or any caffinated beverage will attack your adrenal gland badly. Realy hard. Your adrenal gland is responsible for your adrenaline (duh) and gets triggered by the caffeine. So, it's not the caffeine that gives you a boost, but the adrenaline that gets released. Until it's gone, drought up, vanished. You can drink Red Bull till you die, but the adrenaline won't be there. Until you fix it.<p>You see, your body is a bank. A bank full of nutrient to be released when some other part of the body needs it. If you never make deposits, you won't get any interest either. If you only make withdrawals, you will end up with debit. If you continue you go bankrupt and die.<p>Healthy hackathons? I guess it's possible. I eat a lot of butter from grass-fed cows. I use omega-3 a lot and magnesium. My brains work much better and that without any caffeine. There are other supplements one can use, but always with moderation and enough sleep. Without sleep, your hormones won't get any rest or balance.<p>Hackers who think they have super powers and don't need sleep are having a Wall-Street mentality prior to 2008. Grow up, you only have one body, so you better take care of it.
<i>>Make the stretch longer. Let's say, three days, from Friday evening to Sunday night, so there would still be time if the participants slept through the night.</i><p>Like a hacker test match. What a pleasing image.<p>There should be tea breaks.
I've thrown some hackathons at work and this is the model we always use. Friday after work + dinner we brainstorm and figure out what to do and then we might prototype a bit. Saturday we meet again refreshed and hack, we dont stay up to late and might even go for beers. Then we meet for another 4-5 hours on sunday to make a wrap of it.<p>Personally I can enjoy both the 24-hour/whatever-hour stretch and the weekend-with-rest style, but I find the first one to require working with someone with whom we feed energy to each other so we can maintain progress — I've just met one such person in my life and he doesn't live in the same country as me anymore.
So in the end I prefer the weekend style hackathon now as well.
You've just described Rails Camp.<p>I'm off to the next Rails Camp Australia in a couple of weeks: Friday afternoon to Monday morning in the beautiful Gold Coast hinterland. Anything goes - hacking, coffee, beer, exercise, partying or sleeping, and even camping.
overall, we did a lot of what you suggested at PennApps. I think the key is to provide an avenue for both types of hackers: if you want to stay up all night, we have Red Bull and late-night give-aways. If you want to sleep, we have a quiet area with portable hammocks or sleeping bags. Healthy food is available throughout and organized exercise is available to those who seek it out.<p>By the way, if you (hackathon organizer) have the budget for it, bringing in masseuses (15 minutes per person, sign up/raffle spots off) is an amazing Saturday break. Sponsored by pick-your-favorite-VC.
> I really felt like going home and have a good night sleep. But I didn't want to let your fellow hackers down<p>This is the tricky bit, because it's where our social instincts give the wrong answer, and it's important to be able to recognize it because it happens in other contexts than hackathons.<p>In reality, if your teammates want to stay at work all night, you are letting them down by joining them, because you are reinforcing their irrational and self-destructive behavior as well as damaging your own ability to contribute. The best thing you can do for them is go home and rest so you can work productively tomorrow, tell them to do the same thing, and hope the message will eventually get through.
Why would anyone think they can write good code without sleep? I need my sleep to function and will not go to any contest or event where sleeping at night is not an option.
Game jam Melbourne pretty much does this. Friday to Sunday, facilities to sleep and shower. Food and drink (with healthy choices) available. Those that were most productive probably were those that went to bed at a reasonable time the first night.
I never try to kill my self at Hackathons. Go to sleep when you are tired and dont eat crap. At some point you are bound to get only diminishing returns, you should know this by now if you are all grown up.
This is how we do things at ZocDoc actually (<a href="http://engineering.zocdoc.com/post/19991240421/winter-hackathon" rel="nofollow">http://engineering.zocdoc.com/post/19991240421/winter-hackat...</a>) and it really is great. We start thursday evening and finish on sunday, there are definitely late nights but plenty of sleep. The timespan is more than reasonable to finish a project. Definitely the best way to do a hackathon.
That's why over at Berkeley we at Hackers at Berkeley decided to start hosting Hackjams. They're twelve hour events from about 1 PM to 1 AM. We have much less pressure, more emphasis on fun and trying things out and showing what you learned, even if you don't have anything approaching a product (I once showed an awful demonstration of all that I had managed to learn about Three.JS in five hours).
I absolutely agree with the article. Most people don't realize that their productivity will become shitty if you introduce little sleep, bad food and no exercise - so why would you artificially work with exactly these things to finish your product?
48 or 72 hours total time spent developing an application should be ample time to have something bootstrapped. I don't mean 3 days, I mean total time working on a project.<p>I've found that if I go over the 72 hour mark, I begin to lose interest
Whenever we (<a href="http://brighterplanet.com" rel="nofollow">http://brighterplanet.com</a>) sponsor hackathons we always do a "Healthy Hacker" component, with yoga, healthy food, etc. e.g.:<p><a href="http://numbers.brighterplanet.com/2011/04/12/healthy-hacker-photos/" rel="nofollow">http://numbers.brighterplanet.com/2011/04/12/healthy-hacker-...</a>
<a href="http://numbers.brighterplanet.com/2012/01/27/cleanweb-hackathon-nyc/" rel="nofollow">http://numbers.brighterplanet.com/2012/01/27/cleanweb-hackat...</a>
Do multi-day marathons for runners, swimmers, and other sports athletes go continuously 24-hour or do they have a way to fairly sleep each night? If so, is there anything to be learned by how traditional sports handle this issue?<p>I read somewhere that some races take a time snapshot of when the athletes arrive at a sleeping stop and use it to determine when they can resume the next day.
I would recommend taking a look at <a href="http://hackdaymanifesto.com" rel="nofollow">http://hackdaymanifesto.com</a><p>Also as someone who has runs about one community event be it hackday, designjam or barcamp a month I have learned to cater for everyone as best as possible.
I agree, especially on the food & drinks and on physical exercise.<p>That's why hackerspaces are better imho. You don't have to rush an idea to be finished in a weekend.
If you increase the length of a hackathon (from 1 day to 2, or 2 to 3) then you'll just increase the expected output, people likely won't take it easier.
This isn't rocket science, put explosive fuel in your body and you sprint for about 6 hours, and then you crash and need 5 days to recover. Ignore the warnings and drink these poisons/fuels several times a day and you'll burn yourself out after 3 to 10 months and decide that botany isn't as bad a career path as everyone says. Burn out is your body telling you that the red bulls are killing you.