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]

``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:Enhance?

[Devv]

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:Enhance?

[somersault]

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:Enhance?

[flewp]

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.

Publicity stunt

[mattMad]

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.