This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
Regardless of our background, programming language of choice, or political persuasion, most developers have at least one thing in common: we enjoy building things. As full-on members of the creative class, however, we're also likely to have a million ideas for useful gadgets, web services, and applications, but comparatively little time to execute on them. Sigh.Fortunately, given modern web savvy tool sets, it's easier than ever to launch a website or application. In fact, yo
Regardless of our background, programming language of choice, or political persuasion, most developers have at least one thing in common: we enjoy building things. As full-on members of the creative class, however, we're also likely to have a million ideas for useful gadgets, web services, and applications, but comparatively little time to execute on them. Sigh.
Fortunately, given modern web savvy tool sets, it's easier than ever to launch a website or application. In fact, you might even be surprised how quickly you can roll out a "v1" of a worthwhile service or micro-app, using a framework like Rails or Django. Sometimes all you really need is a weekend, a little bit of motivation, and a willingness to embrace your constraints. That's where code contests come in...
Last year a bunch of other passionate Ruby developers and I tossed together a competition we dubbed the Rails Rumble. The idea was to get developers to set aside 48 hours of their life to design, develop, and deploy a working first version of some web-based app they'd been dreaming about (yes, this post will border on shameless quasi-self promotion, but it's for a good reason, really!). After the weekend development sprint wrapped, the community at large was given the chance to vote on the fruits of that labor, rating entries according to their user interface, usefulness, completeness, and level of innovation. The highest rated applications won prizes supplied by event sponsors.
But the real purpose of the event wasn't about winning or losing, it was about motivating developers to see what they could do given some very constrained resources (Rails, small teams, 48 hours). We wanted to give people an excuse; an excuse to take one weekend and build something. Launch something. 140 teams of developers participated in the event and almost 100 of them were able to deliver a usable, working first version of their service within the timeframe. That's pretty impressive, for a weekend of work, and many of the entries were truly inspired. A number of them, including grand prize winner Tasty Planner, have seen continued development and become useful and well-loved services outside of the contest they were launched in.
The morale of the story is that you can accomplish a lot in a single weekend ... you just need a little motivation, maybe one or two other people who are similarly invested in building something great, and a finish line to focus on. And of course, you need a willingness to embrace the constraints of your particular situation. One of my favorite passages from 37 Signals' Getting Real makes this point over and over again;
There's never enough to go around. Not enough time. Not enough money. Not enough people.
That's a good thing.
Instead of freaking out about these constraints, embrace them. Let them guide you. Constraints drive innovation and force focus. Instead of trying to remove them, use them to your advantage.
So don't fight it. Figure out what you can do with what you have instead of wishing, wondering, and wallowing.
Of course, you don't necessarily need to participate in a startup competition or a code contest to do this, but the thing that's fantastic about the structured competition as a launch pad is that it imposes these hard constraints such that you tailor your goals to fit the timeframe and opportunity. The friendly spirit of competition doesn't hurt either, nor do the prizes. And there's also the fact that events like this tend to get a little media attention, which gives you an instant user base to experiment upon and get the word out about your application.
If you're interested, the 2008 Rails Rumble event will be held the weekend of October 18th and 19th. Registration will open within the next couple weeks. If you don't know Rails but this sort of thing still sounds interesting to you, don't worry. There are other competitions that may be closer to your area of expertise -- Startup Weekend and Blitz Weekend present similar challenges, for example. A quick google search should turn a few up additional events. On the other hand, you could also use it as an excuse to learn a new toolset, one that serves a number of people extremely well for quick prototyping and building powerful websites and micro applications.
Whether you're looking to get involved with the Rails Rumble, Startup Weekend, or just looking to set aside a weekend (or two) of your own time, the message is still the same -- embrace your constraints and get something working asap. The first version of your vision probably isn't going to be bug-free or have a perfect user interface, but that's okay. Get something out there for users to play with that represents the core of your idea, and then use the feedback of your friends, fans, and peers to continue to bake it until it's just right. You may even end up taking it in a direction you never expected, once some external criticism is added to the mix.
Stop worrying and love the launch!
We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.