proustiskeen wrote on 01/03/18 at 17:37:23:
These articles mainly try to convince the readers how important it is to analyze one's own games. It only scratches the surface about how you should analyze one's own games.
When I talk on my blog about analyzing my games then I focus on the technical aspects.
1) When to use full analysis/ deep position analysis/ monte carlo analysis, infinite analysis.
2) Does it makes sense for e.g. 1600 rated player to check his analysis with Komodo and then once more with Stockfish, Houdini,...
3) How much time should I give the engine to analyze a game?
4) Which databases should I check for the opening?
5) From which move onwards should I check the opening as clearly from move 1 does not make any sense?
6) Should I use tablebases for the endgame and how?
7) What is the benefit of backwards analyzing?
8) From which point can I consider my played move a mistake?
9) Should I also look at alternatives for every move and what exactly is an acceptable alternative?
10) Should I add comments to the analysis and which comments?
11) Can I remove (bad) analysis as sometimes the file becomes unreadible? How do you deal with that?
12) Should I revise analysis made of years ago or can I let it rest?
13) How often should I check for new versions of engines, databases, hardware? Can I skip some releases....
14) Which shortkeys do you use often? Do you have developed some special tools/ other techniques?
All this I discuss on my blog and much more. For me that are the questions which people are searching when they want an answer about how to analyze one's own games.