I agree with you to some extent. But there are some points on which I have a different point of view.
The aim of a hackathon: The aim is to provide a distraction free environment. On normal days, can you and your teammates work on a cool project uninterrupted for more than 2 hours? Doubtful. Plenty of distractions like WhatsApp, Instagram, FB etc. But in a hackathon - you can actually make something worth sharing.
The food provided isn't healthy - sure, but they don't put a limit on water do they? You have to stay hydrated. Also most hackathons are organized by students who don't have a budget for a proper meal.
Regarding only naive young devs participate. I think there is a solution. Senior devs should guide the junior devs to make the product in the timeframe. They don't necessarily be present for 36hours. They can rest making the case for back-pain and mothers valid.
Coding and socialization is a tough one. Doing both together is really hard. Can't argue there.
Most hackathons project don't go anywhere- in India sure. But what I learned from that time was invaluable. Sure the burnout was real and I didn't code for 2 weeks after. But don't look at the short term, my experience was very valuable later and I learned somethings on which I reflected on in those 2 weeks.
The aim of a hackathon: The aim is to provide a distraction free environment. On normal days, can you and your teammates work on a cool project uninterrupted for more than 2 hours? Doubtful. Plenty of distractions like WhatsApp, Instagram, FB etc. But in a hackathon - you can actually make something worth sharing.
So this is actually why I proposed a "hackathon" at my company where developers are not to be interrupted for a stretch of time. That allowed them to focus and come up with some really cool prototypes.
I agree with you to some extent. But there are some points on which I have a different point of view.
Most hackathons project don't go anywhere- in India sure. But what I learned from that time was invaluable. Sure the burnout was real and I didn't code for 2 weeks after. But don't look at the short term, my experience was very valuable later and I learned somethings on which I reflected on in those 2 weeks.
So this is actually why I proposed a "hackathon" at my company where developers are not to be interrupted for a stretch of time. That allowed them to focus and come up with some really cool prototypes.
If you are referring to 8 hours - I believe you need more time than that to translate an idea to code. In my opinion 24-36 hours are optimum.