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.'"

37 of 154 comments (clear)

  1. Pardonez-moi by MrEricSir · · Score: 5, Insightful

    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."
    1. Re:Pardonez-moi by Anonymous Coward · · Score: 5, Insightful

      I for one was shocked to find out that if I entered a contest, there was a possibility I might not win. My mom always told me I would succeed at whatever I tried. Does this mean that I might not get $75 million dollars for the lottery ticket I bought this morning? I wish someone had told me that before I quit my job.

    2. Re:Pardonez-moi by biobogonics · · Score: 5, Insightful

      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!

      How is this situation different from any other so called "talent" contest? Look at the dancers who did not win on "So You Think You Can Dance?". It's the same reason for the spread of "reality" TV. These shows are inexpensive to produce - just like game shows were.

    3. Re:Pardonez-moi by Rivalz · · Score: 2, Insightful

      Yes I often go to various companies I intend to work for. Offer them each to pay me in advanced for the chance I might choose to work for them.
      I of course will not refund the money as they had the privilege of competing for me to select them for my place of employment.
      The problem with my argument is no one in their right mind would agree to it.
      So why agree to a contest on the off chance you are one of two things (Extremely over qualified / talented enough to beat everyone else) or (Not doing it for the money and would do it anyhow).
      Chances are you want to know you are the best but really you arent. You are just the best of a group of people who want to prove they are the best or looking to get lucky.

    4. Re:Pardonez-moi by HelioWalton · · Score: 2, Funny

      Joke spoiler alert! The "protection racket" link was an insinuation that Rivalz is not someone they would want working for them and that they would go to extreme lengths to prevent him working for them...

    5. Re:Pardonez-moi by Fulcrum+of+Evil · · Score: 2, Interesting

      So you're OK with contests used as a substitute for hiring people to work on your projects?

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    6. Re:Pardonez-moi by edmicman · · Score: 4, Insightful

      Yes, if the people entering the contests agree to the terms and conditions before-hand. If I say 'hey, do this work for me for free, and I won't offer you any compensation' and someone willingly does it, what the heck is the problem? Are we in Bizarro World today?

    7. Re:Pardonez-moi by sohp · · Score: 2, Interesting

      There a many corporate-sponsored contests like this photography, mostly geared at amateurs. Back in the 80s I learned to look at the terms carefully, and if anywhere in them was a clause giving up rights to the photographs entered to the contest-holder, to run far away. Prestigious contests always make it clear that all rights remain with the photographer, although they may legitimately request a time-limited right to display entries for promotional purposes only, not for resale ever.

      Stock agencies used to use these contests to pick up vast swaths of decent, if unremarkable, photographs for almost nothing, and with no pesky trouble like having to keep track of who took the photo for credit and payment. I imagine now with Flickr and the flood of digital images, they don't really have work even that hard.

      All this remains true for programming contests, and really any contest where the creative work of an individual is made available to another party.

    8. Re:Pardonez-moi by apoc.famine · · Score: 2, Insightful

      The thing is, you can't reliably use a contest as a substitute for hiring people. When you hire people, you interview, pick people with the correct skillset, and then tell them what to do. Contests are voluntary. There's no guarantee you'll get anyone finishing your project. There's even less of a guarantee that they'll finish it to-spec.

      Using a contest in lieu of employees for anything is a gamble. Not enough prize money, and you won't get competent people working on it. You'll also have to spend employee time weeding through all the cruft submitted. Then there's the legal questions about the code submitted.

      Unless you're a big-name company, with a solid reputation, I don't think that we really have to worry about exploitation via contests on any large scale. Even then, I don't know how many times a company could pull it off before everyone started calling out "bullshit". If you publicly pronounce that your in-house staff can't do a job too many times, everyone takes notice...

      --
      Velociraptor = Distiraptor / Timeraptor
    9. Re:Pardonez-moi by Imrik · · Score: 2, Informative

      It's not the fact that you might not win, it's that they can still use your entry (without paying you for it) if you don't.

    10. Re:Pardonez-moi by Teancum · · Score: 2, Insightful

      Using a contest as a recruiting tool, on the other hand, is an interesting way to do thing. Hold a contest and then people may submit their code samples for that contest to solve a small but critical problem for the company. It should give a pretty good idea about how resourceful the candidates might be, how much they follow specifications, and how well they understand a critical problem domain for the company.

      Don't necessarily promise employment, but ask for enough information so you can contact that individual and perhaps offer them the chance to move on as staff to continue to do things like was in the contest on a permanent basis. At the very least, those who participate and get a job offer would be flattered even if they turn down the offer and perhaps there might be a couple desperate people who might say "yes" in such a situation. Nothing gives an ego boost better than a job offer anyway and is in some ways worth more than a prize.

      On the other hand, if a company is using a contest as a means to reduce its R&D staff and hoping to "outsource" that engineering effort through contests.... they are likely not a company you should be working with in the first place. A contest isn't necessarily going to reduce engineering costs and will likely even increase them over the long term as bugs in the source code are discovered or slight tweaks need to be made that may make the "winning" code obsolete. Unless it is a widely acknowledged program in general, it might even show "the competition" where you are weak and what kinds of problems you are facing as a company.

  2. Re:GPL by Lunix+Nutcase · · Score: 4, Insightful

    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.

  3. what about pre / in interview code samples or prob by Joe+The+Dragon · · Score: 4, Insightful

    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.

  4. Let's see some examples of... by John+Hasler · · Score: 5, Insightful

    "...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.
    1. Re:Let's see some examples of... by godefroi · · Score: 4, Insightful

      Of course, if your code pisses off the recording or music industry, then there's no functional difference...

      --
      Karma: Poor (Mostly affected by lame karma-joke sigs)
  5. Re:what about pre / in interview code samples or p by PolyDwarf · · Score: 2, Insightful

    Are there people who work, for free, in a "probation period", where those people are not interns?

    Seriously... If any job I was applying for said "Well, Mr Polydwarf, we like you and all.. but we're going to need you to sit at a desk and pound some code out, just to see if we *really* like you.. Oh yeah, no paycheck, either. But, you do get to bask in the glow of your monitor and congratulate yourself on a job well done."

    Benefits are a different story (a lot of places, they won't kick in until some amount of time in, like 90 days)... But paycheck?

  6. Re:GPL by 0racle · · Score: 3, Informative

    The GPL does not preclude that, though it would still most likely disqualify you from competition anyway.

    --
    "I use a Mac because I'm just better than you are."
  7. Learning for the sake of learning by atomicxblue · · Score: 2, Insightful

    If the runners-up are not selected, it isn't a complete loss as they had a valuable programming experience.

    1. Re:Learning for the sake of learning by retchdog · · Score: 2, Insightful

      nothing's ever a complete loss then. i'm sure even african slaves got good physical exercise in the cotton fields.

      --
      "They were pure niggers." – Noam Chomsky
  8. Terms of netflix contest by catbutt · · Score: 5, Informative

    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.

  9. Drama by Voulnet · · Score: 4, Insightful

    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.

  10. never seen one by OrangeTide · · Score: 2, Informative

    I've never seen a netflix popup/under. perhaps you didn't install enough plugins to block ads and garbage. it's useful for more than netflix, like the million of "your computer may be infected" ads.

    --
    “Common sense is not so common.” — Voltaire
  11. Re:what about pre / in interview code samples or p by Achra · · Score: 5, Funny

    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.
  12. Don't forget the reward by bugs2squash · · Score: 2, Insightful

    The alternative to a competition is what, a request for tender, a bunch of responses from big corporations. At least the competition gives me as an individual a reasonable way to compete.

    --
    Nullius in verba
  13. Re:what about pre / in interview code samples or p by AuMatar · · Score: 2, Insightful

    Where the hell did you work with no benefits for 90 days? I've never seen it go longer than 2 weeks (generally because the health insurance processed forms every 2 weeks).

    --
    I still have more fans than freaks. WTF is wrong with you people?
  14. You can be a devleoper and not know that? by nedlohs · · Score: 3, Interesting

    Obviously if you enter a competition and don't win you spend effort entering for no reward. I wouldn't think it would be possible too drool let alone develop software without knowing that.

    That the prize runner benefits from non-winning entries (if the terms and conditions are as such, and you know them before you enter) is also obvious. That's part of the reason for running one, you might award your million dollar prize for the best piece of crap in a field of garbage and would have been better of hiring programmers (ignoring the promotion beneifits of a competition). Or you might get more and better software than you could have got via hiring for the same cost.

    Attending a job interview, writing a cover letter, tweaking the CV to highlight relevant experience, etc, those all require effort or time - and yet they don't have to offer me the job (or offer me the pay/benefits I want). Oh noes... there's risk...

  15. Re:what about pre / in interview code samples or p by corbettw · · Score: 5, Funny

    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.
  16. This is news? by gurps_npc · · Score: 2, Funny

    No, this is Fark. The 'risks' they mentioned are obvious and belong to almost all contests.

    --
    excitingthingstodo.blogspot.com
    1. Re:This is news? by ADRA · · Score: 2, Funny

      You answered faster than I did! I mean DUH, that's how these contests work. That is why companies release them, and that is why there will always be a niche software market for them. If anything, it really tells us that there is an over supply of talent just wasting away in the market if they all have time to join these contests and get recognition. I don't really know how big this market is, but I can't imagine that the rewards are much above table scraps when you calculate time invested.

      --
      Bye!
  17. Re:what about pre / in interview code samples or p by nedlohs · · Score: 2, Insightful

    What sort of idiot would take a job with an unpaid probation period???

  18. Re:what about pre / in interview code samples or p by fishbowl · · Score: 2, Informative

    >Probation period? Who signs on to a job like that?

    Almost everybody at almost every level. Even when the opportunity has long-term prospects, the offer is usually on a contract basis where the employer defers the option to hire to a benefits-eligible position. This is pretty standard in programming jobs nowadays.

    --
    -fb Everything not expressly forbidden is now mandatory.
  19. Re:what about pre / in interview code samples or p by Ash+Vince · · Score: 3, Interesting

    what stop them from firing you right at the end of the probation period and getting free work.

    Usually the main problem is that the code in question needs further work. It is very rare that developers are worth the time it takes to train them for the first 6 months. When you audit code written by people on their trial period before offering them a full time post you are usually just ensuring that it does not contain any glaring great screw ups.

    The project you give them will usually be very self contained but with a few external things they need to check in order to see how they deal with it. The main reason for this is that at the end of the day you have to audit it so the candidate is fresh in everyone's mind when the final decision is being made. In my experience you will want to give a potential candidate a decision very quickly after his evaluation day. If they were rubbish they probably did not get that far so you do not wan them to get another offer while you make up your mind. If you have given them a project that involved working on more than 5 or 6 files you have to go through every last line that is different and check it before the code is checked in and that can be a right pain in the arse.

    Much better is giving them a dummy project that is going nowhere but builds on a simple area of your existing system. This way they have to look a the existing code and plan their approach but you get an easy audit at 5:30 when they leave.

    I am also fond of giving them a project they have very little chance of completing in the time allotted in order to see how they cope with pressure. Obviously you do not count the fact they did not finish it against them but seeing how they cope with an unrealistic deadline is far more valuable than the code the produce ever could have been.

    The best employee I have ever had the pleasure to work with came to do a trial day on a day which turned out to be a fallback beta release day to a client. Since the program was supposed to have been handed across to the clients test team 2 days earlier but they rushed in some last minute changes we had no choice but to release on that day. We also knew he was good from his interview so we did not want the candidate to get another offer if we mucked him about cancelling with less than a weeks notice. Then our technical lead got sick on the day of the release.

    We went ahead and he found several bugs before the clients testing team. He also showed he was very professional and coped with a very stressful day very well even though he was a recent graduate with no experience on a development team. The end result was him getting dragged to the pub immediately after the day and him being accepted as part of the development team by his co-workers long before management had given him a firm offer (which of course they did, and he accepted).

    While I would never aim to make a potential employees first day as much of a disaster as that I do think you can give people a basic stress test without letting them know the work they are doing is actually a bit of a dead end that does not matter as much as it could. Unfortunately jobs that pay well are quite often a little stressful at times and it pays to see how people cope with this before you hire them. This can also help the employee since someone who copes well is going to get a better starting offer than someone who can do the job well but looks like they will require more managerial input when they are in post.

    --
    I dont read /. to RTFA, I read /. to offend people in ignorance.
  20. Re:GPL by reebmmm · · Score: 2, Informative

    I am a lawyer, but not your lawyer. It seems to me that order would matter.

    If you assign your copyright first, then there is no GPL issue. The GPL simply wouldn't apply. The assignee (i.e., the new owner) did not need the license to use the software. And even if GPL did apply, they are under no obligation to continue distributing it and you have given up your right to do so (e.g., you sold all your rights to them).

    If you make a GPL transfer first, and the assign second, you could have a copy of the software that could subsequently be transfered under the GPL. The real obvious issue is that a properly prepared assignment reps against this scenario. You are likely going to be in breach of the assignment.

  21. Re:what about pre / in interview code samples or p by Lumpy · · Score: 2, Insightful

    REally...

    tell that to the tons of guys that fight with it daily on the Pro recording boards.

    --
    Do not look at laser with remaining good eye.
  22. Re:what about pre / in interview code samples or p by berzerke · · Score: 3, Insightful

    A desperate for work idiot.

  23. Re:what about pre / in interview code samples or p by sorak · · Score: 2, Informative

    I've seen it at a few places, but never worked for large corporations. There was a job secured by a headhunter, where you weren't technically an employee of the company until 90 days had passed (although you did get paid). Then there is my current employer, who didn't provide health insurance for 90 days. I don't think I've ever had a job that gave out Health Insurance without a 90 day period.

  24. Re:what about pre / in interview code samples or p by Anonymous Coward · · Score: 2, Interesting

    Sound in Windows hasn't been a problem for at least fifteen years.

    Good, tell me how to change the volume of the Microsoft GS wavetable synth independently of the wave output in Windows 7. It works properly in XP.