Hi Vivek, Are you satisfied now..? You got replies from good programmers.Vexorian is one of the problem writer on TopCoder.He suggested practice. Do practice..try to solve problems on TopCoder...
Solve all 250 points problems there and look at your confidence.And most important do it for fun... On Mon, May 9, 2011 at 7:41 AM, Simon <sarne...@utas.edu.au> wrote: > I see it like this. > > The problem solving time can be split into three parts: analysis of > the problem, solution coding and testing/debugging. The coding is the > most glamorous, so I guess that's why so many people make a big deal > about it and want to use macros and such to speed it up. If you > really think about it, though, as long as you can type reasonably > fast, hammering out that 100 lines or so of code is not taking up much > of that hour or so spent solving a problem. Using macros to speed > things up is optimising the wrong thing (and if you *are* slow to > type, that's what you need to practise). > > So, the things to optimise are analysis and debugging. Faster > analysis comes from having a better "bag of tricks" (i.e. experience) > and a more disciplined mind. In short: practice --> fast analysis. > As for debugging, make sure you write code with debugging in mind. If > you write code, look at it and go, "Gee, I... hope that's correct..." > take it for granted that it's wrong and you are going to waste heaps > of time debugging it. > > FWIW, here are my specific tips: > * Learn algorithms > * Coding is exciting and everything but, relax, don't touch your > editor until you have an outline in your head not just of the > algorithm but how you are going to implement it > * When you are practising and get something right, look back over your > code and find ugly, hard to debug bits and try to find neater coding > tricks for them. If the code is for a complicated algorithm or > something and you're not sure you could code it again under > competition conditions, code it from scratch again the next day > * Look in your standard libraries and find all the useful things. > Really, do it. Again and again. > * Remember: *you are not trying to optimise code length*. Don't take > shortcuts. Even if the boilerplate of using library functions, > splitting your code into subroutines and wrapping it in classes > doubles your code size, you will probably more than make up the time > in debugging. > > (Caveat: not everything in the standard libraries is worth using. A > good example is the STL attempt at for_each(), transform(), etc, > tools. These are nice tools in other languages but STL doesn't do it > right. Boost does a better job.) > > On May 9, 5:09 am, vivek dhiman <vivek4dhi...@gmail.com> wrote: > > So most of you say that it is only practice that matters the most. Is it? > > > > Guys i can tell you it is not just practice. > > > > Ok I ll put u this way. how come some guys are able to understand the > > problem so fast while99% of the guys take a little time. > > > > These top guys not only understand the problem but they also know which > algo > > to use within maybe 10 minutes that is something amazing and amusing. > > pratice can tlel you what to use. bu what the problem is exactly it takes > > time atleast some time.. > > > > So the question is still open how come some guys are so fast but rest are > > not.. If the difference was not that much I am sure I wud have never > asked > > this question.. > > > > On Mon, May 9, 2011 at 12:15 AM, Sarma Tangirala > > <tvssarma.ome...@gmail.com>wrote: > > > > > > > > > I am a decent programmer and when I started out I too was looking for > those > > > elusive tips and tricks that the top rated programmers know of. True, > there > > > are quite a few "little things" that would separate a good from an > awesome > > > programmer but none the less its all about practice. Just like math or > > > sports! > > > > > Sent from my BlackBerry > > > ------------------------------ > > > *From: * vivek dhiman <vivek4dhi...@gmail.com> > > > *Sender: * google-code@googlegroups.com > > > *Date: *Mon, 9 May 2011 00:08:12 +0530 > > > *To: *<google-code@googlegroups.com> > > > *ReplyTo: * google-code@googlegroups.com > > > *Subject: *Re: [gcj] Re: fast and furious > > > > > yeah! tell us how some guys are doing too fast. > > > > > Do they know the patterns cuz of practice a lot or do they have high > > > intelligence . > > > Or they know some thing which we don't.. there is got to be something.. > > > > > Regards > > > Vivek Dhiman > > > > > On Mon, May 9, 2011 at 12:04 AM, ravi shanker < > ravishanker....@gmail.com>wrote: > > > > >> Hi, > > > > >> Actually there are lot of things but....can somebody share his > personal > > >> exp....how has he prepared...and become the warrior. > > > > >> On Mon, May 9, 2011 at 12:00 AM, vivek dhiman <vivek4dhi...@gmail.com > >wrote: > > > > >>> It's not about macros. I have observed that writing code doesn't take > > >>> even 5 mins once you know what to code. > > > > >>> But these guys are very fast. They figure out the alog in may be 5 > mins > > >>> what algo to use. I mean that is freaking awesome. > > > > >>> ow come they do it. Is it only practice or am I missing something? > > > > >>> All kinds of help will be appreciated. There are lots of rounds to > go.. > > > > >>> Regards > > >>> Vivek Dhiman > > > > >>> -- > > >>> 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. > > > > >> -- > > >> 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. > > > > > -- > > > Regards > > > Vivek Dhiman > > > > > -- > > > 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. > > > > > -- > > > 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. > > > > -- > > Regards > > Vivek Dhiman > > -- > 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. > > -- Thanks & Regards, Satyajit Bhadange http://satyajit-algorithms.blogspot.com/ -- 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.
