f6 is solid, but it limits your development by blocking the knight. Also in many positions (not really this one, but in general) f6 is a bad opening move because it weakens your king.
Bd6 is solid enough, but it's a passive square (e5 didn't need additional protecting) and the bishop blocks the d file.
Be6 was fine (if the engine didn't like it it's for some dynamic reason like tactics, not something like a basic concept you're violating).
Because of your opponent's unambitious play, you got away with it, and even more, by move 10 your position is better. Anyway, these inaccuracies (f6 and Bd6) don't matter so much until you're playing fairly good people at long time controls, so if I were you I wouldn't worry about it for now. I would say these aren't important inaccuracies that you can learn from... or at least, there should be much more important/instructive things lurking in your games.
Hi,
I noticed in analysis the engine seems to prefer moves which relieve tension, at least in the opening. I don't like doing this, though. Here is a game I played (as black) today where many moves that seemed very sound to me are considered mistakes by the engine.
Does anyone have any insight into what some of these mistakes are? In particular I often develop my bishops early in preparation for an attack + allowing them to cover more space and protect the pawns in the center. In this game I do this on 5 ... Bd6 and 6 ... Be6 and sometimes I will move a queen side pawn up in front of a bishop like in 4 ...f6, but this is also considered a mistake.
Can someone provide insight on why some of these moves do not seem to be favored?