4-Minutes To Entry

Hackaday logo with the words "4-Minutes to Entry"

If you think it’s too much work to write about your projects you’re simply wrong, and I’m going to prove it to you.

The first of this set of videos walks though the steps for submitting an official entry… I did it in under 4 minutes.  The second clip covers the extra details you need to post to meet the requirements for the first cutoff on August 20th.

This is the bare minimum needed for your project to be reviewed by the judging panel. But here’s the thing: get your basics down early, then refine as you go along. The Hackaday Prize celebrates the journey of developing interested connected devices. From now until November you should be working on the build and adding to infor to your project post as you go.

Did we mention your odds of winning this thing are really good?

20 thoughts on “4-Minutes To Entry

  1. I tried the hackaday.io site and I am reluctant to offer my opinion on it as I really like hackaday.com site.

    Really – when I go to a project the images jump between two sizes that are close in size. My CPU fan goes berserk and my PC locks up with my browser (FireFox 30.0 on Win XP SP2) uses 100% of CPU resources. Now I personally think there is a lot that could be done to improve the .io site but why would I comment on that when the site is so bad that I can’t even use it. Well here it is anyway –

    I mean … the layout looks like a porn gallery … large images with short meaningless incomplete text.

    I can’t upload code!!!!!!
    Really have any of you used a text highlighting code editor say … in the last 30 years. They have been around for decades. We’re not in the 1950’s … we have colour now or didn’t anyone notice.

    Oh and did you ever notice that coders are picky about the use of white space? I mean real picky! If I upload code to the .io site it is then presented in such a way that I would be too embarrassed to have it associated with me in any way.

    Ever read a electronics reference manual … did you notice images, tables, graphs and code snippets are ALL inline with the text? Did you notice an index with *clear* navigation to find where you want to be?

    All of the above is what the .io site is NOT!

    Add to that – that I can’t even use it with my chosen browser and it’s just a no-go!

    Just to reiterate – I really do like the hackaday.com site and I really would like to upload projects but when it comes to the .io site … burn it with fire!!!!

    And to quote Brian: “More negative feedback than the hackaday comments section” lol.

    No offence intended, I am hoping some of this rant may be taken constructively.

  2. OK, I am going to use this area to vent about the voting. I just used up my last 50 votes for the “Most Outrageous Component” pass. 43 times the “Growerbot” came up as one of the two choices and out of the three rounds of voting I have seen any one of my three projects come up one time while others just keep popping up over and over and over. What gives?

  3. I know a guy who is a resident of Quebec and can’t enter the prize, but would really, really like to. If this guy were to use a family member’s Ontario address would it be noticed?

    1. The rules are impressively complex in Quebec thanks to the Régie des alcools, des courses et des jeux.

      As long as you don’t win the big prize I’d be that you’d be fine with a different mailing address. I’d assume that as long as you can receive the prize at that given address, and you volunteer to pay the 3% lotto tax upon importing into Quebec I’m sure you’ll be fine.

  4. Is it just me or does the rules page say “Create a video, no more than two (2) minutes in length” and the howto says “atleast 2 minutes”
    I mean, I must be crazy or someone would have pointed it out by now, right?
    long and short, I dont know how long to make my video…

Leave a Reply to brainoCancel reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.