Hackontest — 24h Open Source Coding Marathon

maemst writes "Can you code 24 hours non-stop? Hackontest is a new Google-sponsored 24-hour programming competition between different open source projects. Its goals are to enhance Free Software projects according to user needs and to make visible how enthusiastically open source software is being developed. During the current online selection process users and developers of open source software may submit feature requests and rate and comment them. On August 1st, 2008 the Hackontest jury will pick the three most promising teams. Each team will receive a free trip to Switzerland on September 24/25, 2008 to participate in the competition located in Zurich. Hacking 24 hours inside an etoy.CONTAINER, the teams and their virtually present communities will implement certain features based on the online ratings and jury selection. In the end, the Hackontest jury evaluates the code and awards the winners with a total of USD 8500. The jury is made up of 10 renowned open source contributors: Jeremy Alison (Samba), Jono Bacon (Ubuntu), Brian W. Fitzpatrick (Subversion), Martin F. Krafft (Debian), Alexander Limi (Plone), Federico Mena-Quintero (GNOME), Bram Moolenaar (vim), Bruce Perens (OSI founder), Lukas K. Smith (PHP) and Harald Welte (gpl-violations.org)."

Enhance?

[RAMMS+EIN (578166)]

``Can you code 24 hours non-stop? ... to enhance Free Software projects''

I don't know about the rest of you, but, although I am sure I _could_ code non-stop for 24 hours, I am sure I won't be producing the best quality code if I do so. I think _enhancing_ any project is best done with clear thinking and sufficient breaks.

Re:

[jellomizer (103300)]

the common argument ammong tech workers are the long hours... Yet we partisipate in competations to show it off. Mixed messages any one?

Re:

[Devv (992734)]

I could probably hack for 24 hours non-stop but I wouldn't be able to work on a serious project for 24h non-stop
Obviously I am referring to the diffrence between a hack and a serious application built with continued developement in mind.

Re:

[somersault (912633)]

Exactly, I tend to spend more time wondering which direction to best approach a problem from, trying to find an elegant solution that is succinct, but also flexible. I often spend a lot less time implementing and bugfixing code than I have planning it out.. there is more than one way to do it, as them perl people say - often the challenge is just deciding what is the 'best' way to do it for the application you are writing. I'd give examples but I'd just end up ranting for 2 paragraphs, as usual :p

Re:

[flewp (458359)]

I don't know how it is for programmers, but as an artist I've stayed up for more than 24 hours, spending the majority of it on art (be it work, school, etc).

Once I started feeling tired, the quality of work suffered dramatically. No longer was I able to "go by feel" but had to actually think about the smallest detail, and usually it was for the worse.

Re:

[SanityInAnarchy (655584)]

I'm not sure that's quite what GP meant.

I know that I can code, break, and code for some 18-20 hours, with very long breaks -- some to think about the project, and plan it out, and some to get my mind off the project entirely. But by then, the quality really does suffer, no matter how carefully I plan -- lack of sleep eventually makes me completely ineffective at anything, including coding.

I could probably do it with polyphasic sleep, but I'm not sure I have enough time to get on a polyphasic schedule befor

Re:Enhance?

[Bruce Perens (3872)]

Nobody said the judges were being up for 24 hours. In fact, I made sure they knew I wasn't volunteering for sleep deprivation. And I just found out about this strange cyber-morturary container they propose to hold the contest in. Now, we know these things don't always get delivered, but if it does, I want a picture!

Bruce

Re:

[Bruce Perens (3872)]

Oops, it's not the cyber-mortuary, it's another product of eToys, also in a container. Coffin offices, sort of, but then freight containers aren't so small. That's reassuring. When I read the mortuary part, I wondered what sort of plans the organizers had for us :-)

Re:

[Metasquares (555685)]

They're probably going to give the winners jobs. Spending 24 hours straight coding in a coffin is good preparation :)

Re:

[modir (66559)]

The website states clearly that you have to be in a group of 3 people. So it depends on how you manage the team. Everyone has only to work for 8 or 9 hours if you plan it like this. Then as well from the website: "However, the Hackontest developers may connect to their outside community through chat, SVN, wikis etc. thus enlarging their team size virtually in a unlimited scale." In other words those in the container could only be the team leaders/project managers and those outside program.

Re:

[Have Brain Will Rent (1031664)]

Mod parent up - this is a ridiculous way to get new code into software. Sheesh, no wonder half the bug/security fixes I see coming through Ubuntu updates are buffer overflow vulnerabilities.

24 hours a day?

[moderators_are_w*nke (571920)]

Doesn't sound like a sustainable pace. [wikipedia.org]

The question is...

[Devv (992734)]

Does the container have a toilet?

Re:

[Eevee1 (1147279)]

They'll be flushed with success.

Re:The question is...

[WK2 (1072560)]

Sure does. It's a hybrid toilet/deskchair.

Re:

[DeadDecoy (877617)]

They should, otherwise they'll suffer from buffer overflow errors.

int TOO_MANY_BURITTOS = 10;
byte poop[TOO_MANY_BURITTOS];

void codeToMuch(byte *poop){
    char *toilette;
    //toilette = (char*) malloc (TOO_MANY_BURITTOS * sizeof(byte));
    memmove(toilette, poop, TOO_MANY_BURITTOS * sizeof(byte));
}

There is no question...

[Yetihehe (971185)]

It WILL blend your brain.

Publicity stunt

[mattMad (1271832)]

To me this sounds like a publicity stunt with little useful output for the projects. I prefer the concept of the Google Summer of Code (even though many of the projects funded there seem to fail), because it focuses on a longer-term development and possibly recruits new talent to the projects.

Hopefully...

[John Hasler (414242)]

...none of the resulting code will make it into production. Marathon coding sessions produce only crap.

Re:

[modir (66559)]

The link to the etoy.CONTAINER is not the best. The link goes to another project by etoy (which is based on the container idea as well). For more information about the containers you better visit this:
http://www.etoy.com/projects/etoy-tanks/ [etoy.com]

Re:

[Metasquares (555685)]

That page also has a poor explanation. My guess is that the company isn't all that great at clearly explaining what their products do.

Harder to cheat.

[SanityInAnarchy (655584)]

Put everyone in a box. That at least proves that they wrote it themselves.

Missing the point

[Enderandrew (866215)]

It seems everyone is missing the point. I doubt projects will be greatly improved more so in one day through this contest than they would be as opposed to normal contributions in a day. And sleep deprivation may lead to sloppy code. And the contest isn't inherently fair is people have internet access. But none of that is the point.

The prize is small, but the real reward here is PR for the OSS community, and these projects. OSS projects thrive on high visibility.

Re:

[IamTheRealMike (537420)]

What I want to know is what text-to-speech engine was used in the video. Damn, that is the best one I heard yet.

Re:

[SL Baur (19540)]

They asked me, but I turned them down. Better read between the words on that one.

(If) they (had) asked me, but I (would have) turned them down (because I think the whole idea is silly).

There, fixed that for myself.

Yeah, it's unfair that vim (which is a really bad version of vi, give me nvi any day) got representation and we didn't.