Author: Uri Blass
Date: 08:12:47 03/08/02
Go up one level in this thread
On March 07, 2002 at 15:47:19, Roy Eassa wrote: >On March 07, 2002 at 13:38:13, Christophe Theron wrote: > >>it would drain a lot of energy from me to keep >>concentrated enough to not miss 4 or 5 plies tactics. >> >>It is strange because programming is a little bit like that. When you want to >>make a change in a program it's like computing chess tactics: you have to >>foresee all the consequences and all the places where some change is going to be >>needed. > > >I have made this analogy between chess and programming in the past. A design >specification is sort of like a strategic plan. Individual lines of code are >sort of like individual moves. But one major difference: take-backs! In >programming you can always go back and fix your blunders. A programmer who does not need to go back to correct bugs has an advantage. The possibility to go back is not enough and you have to know that you did a blunder to correct it. There are cases when programmmers simply add a new bug to their program when they even do not know it(for example Fritz7 had a castling bug when it did not consider long castling in some cases). The new program may play better because the new bug is not the only change. The castling bug is easy to see but some wrong evaluation that the author did not mean to is not so easy to see. I believe that being able to improve the program without creating bugs is a big advantage. Uri
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.