in fact, i dont think the raw coding speed will be significantly different, if you use any of the high level languages. The key issue is whether u can figure it out how to solve the problem in your brain first, i think that will take much of the coding time, than the raw typing time.
On Wed, Sep 2, 2009 at 2:07 PM, Douglas Drumond <drumond.doug...@gmail.com>wrote: > But for big input files, 8 minutes might not be enough, I don't know. > I'll try some examples today, before qualification round begins to see if > it's feasible. > > > > On Wed, Sep 2, 2009 at 3:03 AM, malugu satyajit <malugu.satya...@gmail.com > > wrote: > >> I guess it should be ok.. 4 minutes is a long long time ;) >> Development speed is what gives us points here. >> >> >> On Wed, Sep 2, 2009 at 1:43 AM, Douglas Drumond < >> drumond.doug...@gmail.com> wrote: >> >>> It would be nice. I'm thinking in doing it so, but I'm a little afraid of >>> running speed. >>> >>> Douglas >>> >>> >>> On Wed, Sep 2, 2009 at 2:35 AM, malugu satyajit < >>> malugu.satya...@gmail.com> wrote: >>> >>>> For this contest, is anyone coding in Ruby. I thought it would be a good >>>> choice because of its brevity and coding speed. >>>> >>>> >>>> -- >>>> Satyajit >>>> >>>> >>>> >>> >>> >>> >> >> >> -- >> Satyajit >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-codejam" group. To post to this group, send email to google-code@googlegroups.com To unsubscribe from this group, send email to google-code+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-code?hl=en -~----------~----~----~----~------~----~------~--~---
