On Thursday, May 3, 2018 at 1:07:09 AM UTC+8, Salvo Isaja wrote: > Actually, they did explain the reasons, although you might disagree with > them. I tend to agree with them, as this turns in a more genuine engineering > experience, but I recognize it is harder than before.
All their reasons basically come down to "screw you, we don't want to help you debug!" There is absolutely no valid justification for that, considering that this is for *practice* (they even explain how to solve the problems!) In a real world situation you can often work with the client to fix the problem, e.g. by getting extra debug info. Also, this will mainly stop the people who need the most help (yeah, kick them when they're down!) For the rest, it will just cause more pain, frustration and wasted time that could have been easily avoided. > As for Ricola's solution, yep, the overflow in maxTime calculation is a > problem for sure. The maximum possible time can be as high as 10^9*10^9+10^9. Yes, maxTime is the start. As I said, that's where multiplications are involved. -- You received this message because you are subscribed to the Google Groups "Google Code Jam" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-code/753b87ef-3e82-4719-a891-9c37ddca1f51%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
