Let me ask you guys a questions, the people who say that Hackathons are great. Why 24 hours? I find that I need to clear my mind after four or five hours of technical work. If I do that, I get a lot more done. And my projects come in 4-5 hour chunks of code writing and debugging and everything else that goes into the development process. A bit, but actually very little, requires or even benefits from face to face tal…
I like the idea of getting together to demo stuff you are working on more than hackathons.
Hackathons are nonsense
71–73 of 73 posts
Re: Hackathons are nonsense
#72Let me ask you guys a questions, the people who say that Hackathons are great. Why 24 hours? I find that I need to clear my mind after four or five hours of technical work. If I do that, I get a lot more done. And my projects come in 4-5 hour chunks of code writing and debugging and everything else that goes into the development process. A bit, but actually very little, requires or even benefits from face to face tal…
Some more of my thoughts on hackathons here:
http://musicmachinery.com/2012/02/20/hackathons-are-not-nons...
Re: Hackathons are nonsense
#73While some people think "building the software" is the goal, I don't think it is. In my opinion, the real underlying goal is to get people out of their normal environment for a day or weekend, make everyone think differently, prioritize everything, and build connections within the local community. There are very few non-purely-social events that cross programming languages, tech communities, and geographies. Hackatho…