Skip to main content

Win a Prize at Your Next Hackathon

Simple Invoice App on the AppStoreA couple of weeks ago I decided to participate in the TechCrunch Disrupt Hackathon. My app, Simple Invoice (www.sendsimpleinvoice.com), ended up winning a prize.  I think if I hadn’t already learned about the vendors’ APIs and come up with some ideas before the Hackathon I would never have had a chance.  Here are a few tips for you to win your next Hackathon!

Think ahead. First and foremost, take a look at the Hackathon website and learn about the sponsors ahead of time.  If the first time you learn about the sponsor APIs is during the event, you are probably behind.  That’s the big reason why popular APIs like DropBox, Twilio, and Twitter always get a lot of hacks – people already know them and might even have some code stashed somewhere.

IoT > Mobile > Web. The second tip is to use hardware if you can help it.  In terms of the things that are most likely to win prizes, I have noticed that wearable technology is perceived more advanced than mobile apps, which in turn generally beat pure web apps.  If you have a choice between building then keep in mind that IoT > Mobile > Web.

Involve technical evangelists. Next tip: always involve the evangelists from the API companies.  They can help you; they can debug their own code and they can guide you in the right direction.  Don’t forget that they want you to be successful because a great app using their platform gets them on stage and in the news!

I worked closely with Evo Snap team and they helped me quite a bit.  They have several different APIs and one was easier to call from iOS than another.  They were also able to give me internal error codes when I couldn’t figure out why my parameters didn’t work.  Without their involvement I wouldn’t have been able to complete my app in time.

Practice your pitch. Practice your presentation and make sure that you can deliver it in less than the allotted time.  It’s always good to have a few extra seconds to add a joke in if you think of something funny.  At TechCrunch Disrupt, we had 60 seconds per presentation.  Here is a link to my pitch – I tried to waste zero time:
http://techcrunch.com/video/simple-invoice-presents-at-techcrunch-disrupt-hackathon/518403996/

A good app with a bad presentation is unlikely to win.  The judges do not have time to go through all of the apps, so they will likely only pay attention to the ones that caught their attention during the first round of presentations.

Establish a web presence. The last thing is to hire a designer and direct part of his/her time into putting together a one page website.  I grabbed a template and put together quick information on a one page website: www.sendsimpleinvoice.com.  The template cost me $13 and I just filled out all the info.  Between registering a domain and launching the site on Digital Ocean, I only spent a couple of hours on the whole thing.

Good luck in your next Hackathon! They are fun, they are winnable, and they offer a great opportunity to learn about new technologies.

PS:  you can download my app here https://itunes.apple.com/us/app/send-simple-invoice/id917501386
PPS: If you liked this post you might want to check out the post about using Test Flight and about Starting a Mobile App Business.
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…