Slashdot Mirror


Google Code Jam 2003 Announced

An anonymous reader says "O'Reilly Developer News is reporting details of the newest Google programming contest, Google Code Jam 2003. Prizes range from t-shirts to ten grand and you can use any programming language you want to solve the increasingly challenging problems." Update by J : ... as long as it's Java, C++, C# or VB.NET.

6 of 303 comments (clear)

  1. C++ only? by pigscanfly.ca · · Score: 4, Interesting

    If I write C code that compiles under C++ would that be considerd "C++" (for the purpose of said competition . While I can program C++ if its a timed competition C would be faster for me) .

  2. Looking for telecommuters? by RobertB-DC · · Score: 4, Interesting
    This is an interesting way of looking for recruits. An individual interview is one thing -- I've seen some real losers get past that process. Google seems to be looking for a way to entice and reward developers who can use their l33t coding sk1llz in a team environment. It's one thing to be able to write good code -- the ability to work with other great coders is valuable indeed.

    Here's what Google values, from their Job Opportunities page:
    What we look for when hiring great people:
    * People with broad knowledge and expertise in many different areas of computer science and mathematics, including distributed systems, operating systems, data mining, information retrieval, machine learning, performance optimization, algorithms, user interface design, statistical inference and information theory, and related areas.
    * People with world-class programming skills.
    * People with excellent communication and organizational skills.
    * People who are passionate about their work and are great colleagues.
    * People who enjoy working in a high-energy, unstructured environment on very small project teams to build amazing products used by millions of people every day.
    * People with diverse interests and skills.
    What intrigues me personally is that this contest takes place in an online collaborative environment. Does this mean that Google is considering opening up to remote working -- as in, I can live in Dallas and "work" in the Googleplex? As much as I'd love to work at a place like Google, there's no way I'm moving to Cali-fall-into-the-ocean-fornia.

    --
    Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
  3. Re:Cheap Labor by WIAKywbfatw · · Score: 4, Interesting

    When your stuck on how to code something....
    run a competition and let others do the coding for you.

    oh and don't forget to through in a t-shirt or to for all the hard work


    And lather, rinse, repeat if you're after some original designs for t-shirts for your website...

    To be honest, I like the idea of this Google competition. I'm not going to be winning it (my programming skills aren't fantastic) but it's a great way of fostering relationships between you and your user base, finding good coders (and potential future employees), getting some good code and/or code ideas and, above all, having a little bit of fun with the community as a whole.

    If all companies were like Google then we'd all be happy as Jay and Silent Bob at a weedfest.

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  4. TopCoder competitions low on quality by Agave · · Score: 5, Interesting

    the way to win a TopCoder competition is to not only be analytical enough to figure out the solution but also to able to type quickly and accurately as well as to take shortcuts like using short variable names. I certainly wouldn't want any 'TopCode' in a production system.

    I was disappointed with my experience in the TopCoder competition at Java One because even on day three, when I was comfortable with the TopCoder IDE, knew that speed was king, and I knew the solution right away I was still beaten out by over two minutes. I mean, I knew the solution, typed it in, compiled first time, ran a test case, passed, and submitted the solution. Damn near perfect in my mind but I was very low man on the totem pole time-wise (~4min vs ~2min).

    I guess learning to touch type by MUDing just doesn't cut it :)

    flee
    flee
    flee

  5. Re:TopCoder! by Thuktun · · Score: 4, Interesting

    The only problem is that TopCoder style programming contests select for speed of implementation over quality, efficiency, readability, and maintainability. Worse, since your code is challenged by other coders, the more unreadable and impenetrable your code, the less likely subtle bugs in your code will be detected in the short challenge period.

    Still, it was nice when they were awarding $300 for first place in your room in Division I for contests every week. When they dropped the prize money for weekly matches, there wasn't a compelling reason to spend my time on it.

  6. Re:TopCoder! Is Pure Evil by tempny · · Score: 3, Interesting

    There are many things that make a coder good. Insightful and elegant design are one. But being able to quickly bang out a solution for a self-contained problem quick and dirty style is just as sure a sign of skill, to me at least.