4 ms·

Wow. These were made in two days? Incredible!

DuskStar 13y ago
About 22 hours, actually. Hacking started about 11am Saturday, and ended 9am Sunday. It was a really short one!
lettergram 13y ago
Many submissions aren't actually made in the given time period. They usually will bring either a partially to fully complete project (pretty sure it's cheating but yeah).
- tstactplsignore 13y ago
  I don't think this is true, actually. I've been to two major hackathons and had many friends at HackMIT this fall, and this really doesn't occur- in fact, the culture was the exact opposite, people were strongly discouraged from bringing in already existing projects and almost nobody did.
  - 001sky 13y ago
    when are the topics announced, tho? any ideas on that...
    - morgante 13y ago
      There aren't really topics for a lot of the hackathons (including HackMIT). For the "themed" hackathons you'll know the topics at registration (ie. weeks/months beforehand).
      - 001sky 13y ago
        Multiple awards seemed to be sponsored or product unique, that is why I wonder on this point. Certain items I would imaging having a hands on beforehand would be quite leg up. Excuse my mixed metaphors ;).
  - yeukhon 13y ago
    I think what he was saying is people already started researching on what ideas to implement prior to the event. Many people brought in their own Pi and hardware hacks so it isn't like they didn't figure out 1/3 of the hard work. But I wouldn't undermine their ability to piece things together in 18, 20 hours.
- morgante 13y ago
  That's really not the case. I'm a regular on the hackathon circuit and it's extremely rare & frowned upon for people to start building before the hackathon. Plus, if you doubt it, peruse their GitHub's and you can see clear building.
  - prezjordan 13y ago
    You can, of course, edit your git history. The whole thing works on an honor system. Since the community is pretty tight-knit, it works.
  - feefie 13y ago
    What's the best way to find their GitHubs? Do many/all projects make their source available online for people to learn from?
    - PlaidHacks 13y ago
      Most of the teams I talked to, mine included, were using private repos. As much as I trust the community and my peers, it would be interesting to require public git projects during a hackathon. Not only would they be a fantastic learning tool, the potential data visualizations would provide a really cool postmortem.
      - morgante 13y ago
        Somebody actually did just that at hackNY this fall: http://committing.jit.su/ http://committing.jit.su/
    - morgante 13y ago
      It depends on the project, but in my experience many (if not most) people end up making their repos public. As for finding them, I'll often just look up the hackers on GitHub and check if they have new repos. Though that's not always the case. I kept the repo for the hack I made this weekend (http://socialsecurity.io http://socialsecurity.io — antivirus for Twitter) private because I'm commercializing some of the machine learning.

About 22 hours, actually. Hacking started about 11am Saturday, and ended 9am Sunday. It was a really short one!

Many submissions aren't actually made in the given time period. They usually will bring either a partially to fully complete project (pretty sure it's cheating but yeah).

tstactplsignore 13y ago
I don't think this is true, actually. I've been to two major hackathons and had many friends at HackMIT this fall, and this really doesn't occur- in fact, the culture was the exact opposite, people were strongly discouraged from bringing in already existing projects and almost nobody did.
- 001sky 13y ago
  when are the topics announced, tho? any ideas on that...
  - morgante 13y ago
    There aren't really topics for a lot of the hackathons (including HackMIT). For the "themed" hackathons you'll know the topics at registration (ie. weeks/months beforehand).
    - 001sky 13y ago
      Multiple awards seemed to be sponsored or product unique, that is why I wonder on this point. Certain items I would imaging having a hands on beforehand would be quite leg up. Excuse my mixed metaphors ;).
- yeukhon 13y ago
  I think what he was saying is people already started researching on what ideas to implement prior to the event. Many people brought in their own Pi and hardware hacks so it isn't like they didn't figure out 1/3 of the hard work. But I wouldn't undermine their ability to piece things together in 18, 20 hours.
morgante 13y ago
That's really not the case. I'm a regular on the hackathon circuit and it's extremely rare & frowned upon for people to start building before the hackathon. Plus, if you doubt it, peruse their GitHub's and you can see clear building.
- prezjordan 13y ago
  You can, of course, edit your git history. The whole thing works on an honor system. Since the community is pretty tight-knit, it works.
- feefie 13y ago
  What's the best way to find their GitHubs? Do many/all projects make their source available online for people to learn from?
  - PlaidHacks 13y ago
    Most of the teams I talked to, mine included, were using private repos. As much as I trust the community and my peers, it would be interesting to require public git projects during a hackathon. Not only would they be a fantastic learning tool, the potential data visualizations would provide a really cool postmortem.
    - morgante 13y ago
      Somebody actually did just that at hackNY this fall: http://committing.jit.su/ http://committing.jit.su/
  - morgante 13y ago
    It depends on the project, but in my experience many (if not most) people end up making their repos public. As for finding them, I'll often just look up the hackers on GitHub and check if they have new repos. Though that's not always the case. I kept the repo for the hack I made this weekend (http://socialsecurity.io http://socialsecurity.io — antivirus for Twitter) private because I'm commercializing some of the machine learning.