Skip to content

Instantly share code, notes, and snippets.

@tonini
Last active January 15, 2024 20:12
Show Gist options
  • Save tonini/9a78b0f44fb9e57b781fbc96c0fce3e7 to your computer and use it in GitHub Desktop.
Save tonini/9a78b0f44fb9e57b781fbc96c0fce3e7 to your computer and use it in GitHub Desktop.
Chess Games January 24

Chess Games January 24

White - Nf3 https://lichess.org/R0dniToi/white

  • Don't trade active pieces
  • Don't move a piece twice in the open stage, if you can't see another development move of minor pieces, think about the rooks or a piece improvement

Black - Caro-Kann https://lichess.org/gw1M7lge/black

  • Don't be scared of O-O-O, White was definitly start the pawn storm on the king-side, so just easy queen-side castling and then to for the king-side, DON'T OVERCOMPLICATE THE THINKING!
  • Don't waste a tempo on a move like a6 because of incoming knight, just develop if there are pieces still need to be developed. First, check first if the incoming really is dangerous, if not, continue with developmend

White - Nf3 https://lichess.org/h7eovXjm/white

  • check the pawn pushes twice, consider them and calculate them 2-3 moves ahead AT LEAST!

White - Nf3 https://lichess.org/40cnO93S/white

  • exd5 was not good and advancing e5 and threat the knight on f6 would be much better. I need to be aware of these pawn pushes which brings also a threat.

White - Nf3 https://lichess.org/eqiPetQg/white

  • Qxd4 was just bad, can't say more about it. It led to tempo loses and my queen needed to move around too early. :/
  • The blunder of the a rook was outcome of not developing my knight and instead losing a tempo with my Queen too early. I need to be aware of my rook on a, develop my knight on c asap.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment