News for hackers. Stuff that matters.
Re:Google Code Jam – Contest scoreboard by just2n on Saturday April 12, 2014 @05:04PM (#7579194)
So all evidence suggests that the 3rd problem is the hardest, by far, which is likely just some number of non-obvious edge cases.

Curious why the "hard problem" disclaimer is on the 4th?

The 4th also has a 90% solve rate (with 50% more submissions) while the 3rd has 44%.

Re:Google Code Jam – Contest scoreboard by raphaelj on Saturday April 12, 2014 @06:03PM (#7579370)
The 4th is definitively the funniest.

In addition to the disclaimer, one thing which worried me was the N <= 1000 in the large problem specification. I got a quite elegant fast solution and a so low bound was really surprising.

Re:Google Code Jam – Contest scoreboard by just2n on Saturday April 12, 2014 @06:31PM (#7579460)
My solution for 4 was quite efficient in design (and very simple). I was able to be very inefficient in the rough implementation (being lazy and copying arrays, reading the entire input file at once and breaking it up into lines in memory) and still, using JS, solve the large set in only a few milliseconds.

That should probably be a few orders of magnitude higher to realistically make the time constraint remotely difficult.

This was a fun problem to think about, though. Naomi is such a cheater.

Re:Google Code Jam – Contest scoreboard by WildUtah on Saturday April 12, 2014 @06:37PM (#7579474)
Please don't give potentially useful hints until the end of competition
Re:Google Code Jam – Contest scoreboard by RookToH7 on Saturday April 12, 2014 @05:08PM (#7579215)
Yeah, that disclaimer scared me off at first. I solved D last, but in the end I do feel that it's easier than C. I suppose you can solve C-small with a more naive method though.
Re:Google Code Jam – Contest scoreboard by mjp94 on Saturday April 12, 2014 @05:17PM (#7579242)
Agreed. I definitely found D much easier than C. Was able to get C small after a failed attempt, but never stood a chance at getting C large.
Re:Google Code Jam – Contest scoreboard by RookToH7 on Saturday April 12, 2014 @06:21PM (#7579429)
The odd thing is, though, I still don't really see how you can solve C-small without solving C-large at the same time (other than actual brute-force). Guess I'll be keeping my eyes peeled for the write-up.
Re:Google Code Jam – Contest scoreboard by pedrosorio on Saturday April 12, 2014 @06:29PM (#7579455)
"other than actual brute-force"
Re:Google Code Jam – Contest scoreboard by pedrosorio on Saturday April 12, 2014 @05:35PM (#7579298)
To be fair, C large has the biggest score of all subproblems.
Re:Google Code Jam – Contest scoreboard by eggie5 on Saturday April 12, 2014 @07:35PM (#7579598)
spend SO MUCH time on the 3rd. I have too much fatigue to even read the 4th now...
Re:Google Code Jam – Contest scoreboard by ebzlo on Saturday April 12, 2014 @08:36PM (#7579717)
Same thing happened to me, but the fourth was so much more fun to solve than the third.