Hackathons are awesome. I try to do like 6 or 7 a year. And I'm married and in my mid 30s.
To take the OP's points one-by-one:
- Hackathons are worth the commitment. They're a fast, efficient way to try out 1) new frameworks and APIs, 2) new employees/cofounders, 3) new ideas.
- Hackathons only exclude people with "lives" who don't choose to make the event a priority. Hackathons filter out timid and less motivated people (and those two attributes are related) and you're generally left with pragmatic people who will make it through the weekend.
- The OP is right. The inconvenience isn't evenly distributed. Life isn't fair.
- Hackathons are only as unhealthy as you make them. Gardening can also be quite unhealthy if you don't wear sunscreen.
- Competition is a positive force, and the extrinsic motivation of judgement and a deadline are real, and good for the hack you produce.
- Since this is a competition, you can't work on a preexisting product any more than you could start a marathon a kilometers up the road.
- They're not just toys. Take a look at POWr.io and Zaarly, both of which came out of hackathons. There are many others, and if anyone knows of some of the top of their head, please reply with them.
I think it's great that people are coming together to help code on your gardening project. Hackathons may not be right for you, but they are definitely right for me and the dozens of ambitious people I've coded with at hackathons over the years.
Hackathons filter out people with shit to do. "Timid" people are not filtered out, except insofar as any competitive environment does. Similarly, "less motivated" people are not filtered out, because it is so, so much easier to crank on something for a weekend, damn the results, than to work incrementally on building something great. One takes a short burst of effort. The other takes significant long-term will. Finding the former to be a waste of resources is not a lack of ambition and certainly not a lack of pragmatism.
I think another important point is that Hackathons are what you make it.
I like going to them to meet new people and try out a new idea. If I want to fall asleep, I can. I'm not "forced" into doing anything I don't want to do.
I usually work 14 hours or so, go to sleep, wake up, shower, then work again - doing this for 2 or 3 days hardly makes me feel like crap or messes with my sleep schedule.
To take the OP's points one-by-one:
- Hackathons are worth the commitment. They're a fast, efficient way to try out 1) new frameworks and APIs, 2) new employees/cofounders, 3) new ideas.
- Hackathons only exclude people with "lives" who don't choose to make the event a priority. Hackathons filter out timid and less motivated people (and those two attributes are related) and you're generally left with pragmatic people who will make it through the weekend.
- The OP is right. The inconvenience isn't evenly distributed. Life isn't fair.
- Hackathons are only as unhealthy as you make them. Gardening can also be quite unhealthy if you don't wear sunscreen.
- Competition is a positive force, and the extrinsic motivation of judgement and a deadline are real, and good for the hack you produce.
- Since this is a competition, you can't work on a preexisting product any more than you could start a marathon a kilometers up the road.
- They're not just toys. Take a look at POWr.io and Zaarly, both of which came out of hackathons. There are many others, and if anyone knows of some of the top of their head, please reply with them.
I think it's great that people are coming together to help code on your gardening project. Hackathons may not be right for you, but they are definitely right for me and the dozens of ambitious people I've coded with at hackathons over the years.