Good stuff as always Nate, I should also reread Pump Up Your Rating- so insightful. BTW I have a whole chapter about FPS in my Chessable course. (coming out Monday!)
Hi Nate, I'm curious, would you also advise the just-in-time vs just-in-case approach when analysing one's own games? When reviewing my own games I fluctuate between trying to really scrutinise every (non-obvious) move and only looking in depth at the moments I've identified as critical/that I didn't understand in game.
I feel like the in depth on every move approach has some extra value as it essentially means more simulation of the calculation/evaluation one would be doing in game, but that it may be less efficient if the extra time it takes to analyse those non-key moments deeply reduces the time one is able to spend on fixing the mistakes identified from looking at those critical moments.
Good stuff as always Nate, I should also reread Pump Up Your Rating- so insightful. BTW I have a whole chapter about FPS in my Chessable course. (coming out Monday!)
Congrats on the course launch! The chess community needs to learn about FPS 😀
Hey Nate …. This sounds like a really excellent activity!
Hi Nate, I'm curious, would you also advise the just-in-time vs just-in-case approach when analysing one's own games? When reviewing my own games I fluctuate between trying to really scrutinise every (non-obvious) move and only looking in depth at the moments I've identified as critical/that I didn't understand in game.
I feel like the in depth on every move approach has some extra value as it essentially means more simulation of the calculation/evaluation one would be doing in game, but that it may be less efficient if the extra time it takes to analyse those non-key moments deeply reduces the time one is able to spend on fixing the mistakes identified from looking at those critical moments.
Context here is analysing longplay OTB games.
Nice article! What were you using in the screenshot to tag chess positions? I don't think I've seen it before.
I am using Notion.