Author
| Message |
|---|
|
|
I found this game to be quite complex for me:
I felt like I was losing in this game starting at about move 8 although Rybka has me with a slight positional edge.
Where things really got hairy was at move 20. I felt certain that I was losing at this point; the main line 20. d5+ Ne6 I felt actually lost for me, but it was the recommended move with me at a 6 point advantage! It took me quite awhile to finally decide on d5+ even though it was the "natural" move.
Deciding on this move actually caused me to take a vacation day because my mind was just so distracted with daily life.
In retrospect, its incredible that I could have such a strong attack and yet feel so hopeless!
Of course the main line which I was agonizing over never actually occurred!
|
|
|
Yep, I'm the same unless I sit down and analyze it. It can be helpful, because it keeps you focussed on looking at the threats.
|
|
|
 Ya it took me so long to just see that the knight on e4 was unprotected.
The problem was I kept seeing 20. ... Ne6 as the refutation and it looked like it shut down my offence so totally and even threatened a future attack (1-ply away with the movement of the king) that I was distracted by all the other lines (like 20. Bxe8 (a bailout), Kg1 (prophylaxis), Nxe4 (attack on the queen with hopes of discouraging 20. ... Bxe3+) without actually seeing that the rook on e8 could not recapture my knight on e4 after Nxe4.
My mind just kept swimming around in circles with me feeling like I was surrounded by sharks. One GM even made fun of that with a statement to the effect that amateurs are so undisciplined with their calculations. 
|
|
|
Players can only "calculate" while engines can "compute." 
|
|
|
I guess that's what Soltis meant when he said that humans are far more efficient calculators than a computer can ever be; we can "know" instantly what a computer must determine by brute force.
You make me realize that this "knowing" can be both a benefit and a detraction; just like I "knew" that the rook on e8 would recapture the knight on e4 (which it no longer could).
|
|
