Slashdot Mirror
The Risks of Entering Programming Contests
snydeq writes "Fatal Exception's Neil McAllister warns developers of the hidden risks of entering programming competitions, which are on the rise since NetFlix awarded $1 million to BellKor's Pragmatic Chaos in 2009. 'Web and software companies offer prizes for a variety of reasons. Chief among them is simply to raise awareness, interest, and participation in a given software platform or service,' McAllister writes. But the practice of offering and entering software prizes is not without concerns. Privacy implications, class-action lawsuits — many of the prizes leave participants vulnerable to prosecution. Worse is the possibility of handing hard work over to a company without reward. 'Contests like the Netflix Prize are sponsored by commercial entities that stand to profit from the innovations produced by the entrants. Those who participate invest valuable time toward winning the prize, but if they fail to meet the deadline (or to produce the leading results) their efforts could go completely unrewarded. Depending on the terms of the contest, however, the sponsor might still be able to make use of the runners-up's innovations — which, of course, would be a whole lot cheaper than hiring developers.'"
But aren't these risks, for the most part, kind of obvious? It's sort of like saying your employer might exploit you for free labor from your unpaid internship. Duh!
There's no -1 for "I don't get it."
That will most likely disqualify you based on the terms of the competition which usually contains clauses about them being able to use your work or some sort of copyright transfer.
what about pre / in interview code samples or probation period coding?
what stop them from firing you right at the end of the probation period and getting free work.
"...prizes leave participants vulnerable to prosecution." I don't see any in the article.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
I think it's only fair to point out that the terms of the netflix contest (which I participated in and got a lot out of) are such that you own everything you produce. I think you may have to licence it to netflix if you win and take the $million, but if so it is non-exclusive.
Let's not make a big corporate drama over everything. Every programmer that enters a contest knows (or should know) that his work may go unrewarded AND into the hands of the contest arrangement panel. If the programmer has enough free time to make something really great for a contest, then he's already a big name or capable of making lots of money and great projects, so somebody making use of his contest entry should be but a little blip on his radar; if his contest entry was that great then he surely can go big time.
Once, in a Microsoft interview, I was asked to write a memory allocator. I always assumed that after I left, the conversation went like:
"Great, copy this down. Tell the next guy to write us a sound driver."
Each processor would proceed sequentially as if it had been better for them not to rise against Saul.
You might think that, but let's face it, memory management in Windows hasn't visibly improved in decades*. Any number of interview candidate submissions could have helped, and yet it hasn't.
Their problem is they weren't sure which one was best; so they used them all, and set up a round-robin system to select which manager to use for which process instance.
God invented whiskey so the Irish would not rule the world.