11–20 of 34 posts
Having been through a couple of Hackathons, rest assured that there are plenty of Hackathons that are more focused on the business case rather than the implementation. I've seen hackathons won by teams that didn't write a single line of code. It was all mocked up in Powerpoint or similar.
> hackathon is a (physical or virtual) competition where people contribute code to you in a manner you decide on and get prizes. Having been through a couple of Hackathons, rest assured that there are plenty of Hackathons that are more focused on the business case rather than the implementation. I've seen hackathons won by teams that didn't write a single line of code. It was all mocked up in Powerpoint or similar.
I'm still on the fence on whether I think this is a good idea or not… It does feel like frabricating/buying github activity with money… but it also does feel like I can't argue that they are doing something with malicious intent…
You can frame plenty github projects with this logic, at the end the community also benefits.
The title of the blog post should be "How to run a Hackathon if your only objective is to trend on GitHub". I've been to many hackathons and also organized a few, and this is one of the most soulless incarnations of a hackathon I've seen. In my opinion on of the coolest things about a hackathon is the ability to live out your creativity and be free from perfectionsim to have a change of pace from your traditional day…
It's because it was released on my blog (Gitroom), so it's the same title. It fits mostly open-source companies :)
> hackathon is a (physical or virtual) competition where people contribute code to you in a manner you decide on and get prizes. Having been through a couple of Hackathons, rest assured that there are plenty of Hackathons that are more focused on the business case rather than the implementation. I've seen hackathons won by teams that didn't write a single line of code. It was all mocked up in Powerpoint or similar.
What sucks is when there's a complete mismatch between those two hackathon approaches. I once went to a hackathon where both engineers and designers were invited; the winning team and the teams with the most praise were all the ones dominated by designers that didn't actually implement anything working, and the more engineering focused teams were pretty quickly dismissed. Worse yet, I was literally the only engineer…
> hackathon is a (physical or virtual) competition where people contribute code to you in a manner you decide on and get prizes. Having been through a couple of Hackathons, rest assured that there are plenty of Hackathons that are more focused on the business case rather than the implementation. I've seen hackathons won by teams that didn't write a single line of code. It was all mocked up in Powerpoint or similar.
What sucks is when there's a complete mismatch between those two hackathon approaches. I once went to a hackathon where both engineers and designers were invited; the winning team and the teams with the most praise were all the ones dominated by designers that didn't actually implement anything working, and the more engineering focused teams were pretty quickly dismissed. Worse yet, I was literally the only engineer…
The title of the blog post should be "How to run a Hackathon if your only objective is to trend on GitHub". I've been to many hackathons and also organized a few, and this is one of the most soulless incarnations of a hackathon I've seen. In my opinion on of the coolest things about a hackathon is the ability to live out your creativity and be free from perfectionsim to have a change of pace from your traditional day…
I really wish there were more non-collegiate hackathons available out there.
The title of the blog post should be "How to run a Hackathon if your only objective is to trend on GitHub". I've been to many hackathons and also organized a few, and this is one of the most soulless incarnations of a hackathon I've seen. In my opinion on of the coolest things about a hackathon is the ability to live out your creativity and be free from perfectionsim to have a change of pace from your traditional day…
It's because it was released on my blog (Gitroom), so it's the same title. It fits mostly open-source companies :)
Earlier quoted context omitted.
It's because it was released on my blog (Gitroom), so it's the same title. It fits mostly open-source companies :)
I think their point was that the title on HN and the blog was inaccurate based on the content of the post itself
And the "in 2024" part... A few ways this can be interpreted:
- How things are going to be different from prior years. First thing that came to mind... "AI tooling must feature a lot now?" Maybe this will be an article about what guidelines to have for use of ChatGPT? (or maybe that it's a non-issue)
- When it was written... seems to be what the author had in mind based on another comment.