3 ms·
It looked like you could view the problem statement first, and then the timer only starts when you download the input file? If so, then write out the solution
by nostrademons 17y ago
It looked like you could view the problem statement first, and then the timer only starts when you download the input file? If so, then write out the solution in full according to the spec, proofread it, then quickly download the input, run the program, and submit the solution. The total time taken is only what you need for program execution and debugging; I could easily see that coming to 7 minutes if you write fairly solid code to begin with.
I'm really tempted to give a couple of these a try, but I'm not eligible (Google employee - heh, never thought I'd be disqualified from a contest for that reason), and I'd rather work on my compiler. :-)
- Tichy 17y agoNo, I think it is the time from the beginning of the project. Once you download the file, you actually only have 4 minutes to submit the solution. (Edit: I just realized that you could look at the problems without logging in. So maybe time measurements only started from the time the user logged in - then you would be right). The only thing is that apparently in the beginning there was a problem with the downloads, so Google extended the available time. Maybe they only started counting time one hour later. 1:30 hours would still be very fast, though. Edit: hm, just thinking, supposing the counting really only started 1 hour later, they could have cheated by letting different people work on each problem. 1 hour per problem seems doable. I don't think the counting really started late, though.
- hc 17y agothe timer starts from the time the contest opened (2 Sep 2009 23:00 UTC).
- mquander 17y agoMy observations: The contest started at 7:00. I didn't visit the site until around 8:45. My first submissions of problems A and B were around 10:00 (because I couldn't submit the first one thanks to the aforementioned problem.) and my time was marked as 3 hours. So I think the timer just started at 7:00 for everyone. I agree that 10 minutes per problem is remarkable and intially shocking, but I think it's correct because it's proportional to the times that the same caliber of programmers get in Topcoder matches (where 3 problems of on-average-higher difficulty are presented with a total time limit of 1:15.)