Re: computer-go: unmake move?

[Don Dailey <drd@xxxxxxxxxxxxxxxxxxxxx>]

   From: "Vlad Dumitrescu" <vladdu@xxxxxxxxxxxxxxxxx>
   Date: Thu, 08 Jun 2000 09:15:52 CEST
   Sender: owner-computer-go@xxxxxxxxxxxxxxxxx
   Reply-To: computer-go@xxxxxxxxxxxxxxxxx

   >What I should probably do is  to profile my  code and measure the time
   >spent making a move  and how much of  this  time is spent  copying the
   >state.  Whether this turns out good for me or not  though, it would be
   >no guarantee that others would get the same  results.

   Hi

   Just my 2 pence worth... In my experience, there is a programming proverb 
   that is just as valid as any Go proverb:

   Don't bother with performance from the beginning; keep the code clean and 
   easily debuggable and maintainable. When you have a working program, then 
   you can start profiling - in most cases the time hogs are not the ones one 
   would expect!

   Good luck!
   /Vlad

   ________________________________________________________________________
   Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com



My thoughts exactly.  For now I wouldn't  change my program even if it
turned out it was somewhat faster doing it the other way.  But I would
later if I reached a point where I felt  the program was really finely
tuned and  this  was the  only  reasonable way to  gain  a performance
boost.  But of course I would  first have to know  that what I'm doing
now is slower, and I don't know that!

Don