I try to review my own games in order to improve (I am maybe 16-15k). For every move that I think is wrong, I try to find a better move. My question is: how do I know the move I find in analysis in better then the one I played? (except for obvious cases, like when a group is killed and I find the move that would have saved it)

Should I use an engine like Crazy Stone in order to check this?

Is there a better way to analyse my games?

  • 1
    If you are ~15k you do not really need to review your own games. Just play more games, you will get stronger. Actually, reviewing your own games right now might be counter-productive, since you will become accustomed to some bad plays. Maybe have a stronger player explain to you briefly one or 2 major mistakes, but then go on and just play more games.
    – Djaian
    Commented Jan 15, 2018 at 14:14

1 Answer 1


Your current approach to reviewing seems good and I recommend you continue this way. If you are not satisfied with a situation, find the reason that led to the situation. Sometimes it is an immediately prior move, sometimes a mistake in fuseki.

If you are having trouble to find the underlying reason, or a better solution to it, you should show your game to someone else who is as strong (more eyes see more) or stronger than you. In the past, there was the Go Teaching Ladder GTL (in which I participated, it was fun!), but it sadly shut down a while ago. You can still ask on KGS in the KTL room. Surely there are some other opportunities, too. One of the things that I find fascinating and enticing about Go is that many people really like to help.

I recommend strongly against using engines like CrazyStone. They always consider the whole board, and will recommend moves that are not helpful in understanding the problem. They might be more valuable when you are strong (definitely dan level, probably high dan level) - but when you are that strong, you can already find better moves yourself. Of course, This may change when stronger engines become available.

I also know of no Go engines that take future positions into account. (I believe it is different in chess!) That is to say, when you believe a certain move leads to trouble (much) later on, even in a sequence that can hardly be deviated from, then there is still not way to make the engine aware of that fact. It will happily suggest moves that are bad, only to notice its mistake a few moves later. It seems to be impossible to fix this in our current tools - search depth grows so quickly that letting it search longer often does not help.

  • 1
    I was going to recommend Crazy Stone, but your argument makes perfect sense.
    – Christophe
    Commented Dec 28, 2017 at 21:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .