A Prototype vs A Hack
In50hrs is an Idea-to-Prototype Event. its been designed that way. Some ask us how its different from a hackathon. We think there are some differences to it, and rather crucial ones.
We've been talking to quite a few folks who run Hackathons - primarily are run by companies to get a developer community build deeper engagement with their platform - and the tune we hear seems common; not enough companies emerge out of it.
In the last one year, over four editions of In50hrs, we've had 100+ prototypes built and roughly 20 odd startups emerge. Are they billion dollar companies? Time will tell, but the evolution of an idea - prototype - product - startup route seems to be emerging.
Hacks don't necessarily become products. Prototypes do. Developers and technologists hack. Product Managers prototype their ideas.
Hacks are solutions to fix a problem - in some cases as a temporary measure. Prototypes are the first step towards creating a long term solution towards a bigger problem.
Most hacks - and hackathons - are a great way to build expertise in a domain, on a platform or in using a tool. Prototypes are slightly wider, constantly keeping the problem that is being solved in mind.
While there are plenty of hackathons around, why are we building a platform for idea-to-prototypes? Because anything that is not managed deteriorates and anything that comes out of a system without the adequate processes is an accident. Rarely do startups, product prototypes and ideas emerge out of sheer chaos. It has to be engineered that way.