Nothing else just practice more and some plugins are recommended for generating both the basic code and the test code more efficient.
good luck On Tue, Aug 11, 2009 at 2:01 PM, Rob Renaud <[email protected]> wrote: > Stay calm. The costs of a debugging a bug are still relatively enormous in > terms of development time. Rushing has a negative expected value, > occasionally it will pay off when you hack out a solution that just works, > but most of the time being slow and deliberate will be much better (is this > off by 1? what happens when n = 0?, etc) will save you oodles of debugging > time and will make it a lot more likely that your submission is correct. > > Practice a lot. > > > On Tue, Aug 11, 2009 at 1:24 AM, FameofLight <[email protected]>wrote: > >> >> Hi, >> >> I am currently practicing on topcoder platform . I often can see the >> solution to problem , but unable to code it in registered time , I >> often commit logic bluder , like condition for if , while etc. >> >> I am coping with this problem for sometime and now I am frustrated , >> can help me out some suggestions to suppress these mistakes. >> >> -Regard >> Hemant Verma >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-codejam" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code?hl=en -~----------~----~----~----~------~----~------~--~---
