I think this is true for many other disciplines, especially programming. You can code all you like, but reading text books on the subject and studying other people's code will quickly improve your skill.
This is something I wish I knew 20 years ago.
This is something I wish I knew 20 years ago.
> You can code all you like, but reading text books on the subject and studying other people's code will quickly improve your skill.
Companies need to prioritize this is the point. It's not about low pay, high pay jobs. Or obtaining a role once you have the skills, it's that companies don't prioritize learning/development as part of the role, they focus on output - and they would get more value from their employees of they did.
You will study other people's code on the job and code reviews provide coaching.
Chess is much harder for me because I don't have the discipline to study like that.
With coding, I can read a quick blog post or follow a tutorial, then immediately start incorporating ideas into my work.
In chess, if I study something, I might not encounter a situation where I can use that knowledge in game for a while. I don't get that immediate reinforcement so I forget things much easier.
If it's mid game it's going to be strategy, you're not going to ever repeat it, so you can apply the strategy in general terms.
If it's endgame then surely you can setup scenarios and play against engines.
Maybe, if it doesn't exist, there's a need for a game engine that will try to do a particular opening to give you practice, will try, say, to fianchetto or castle early (I imagine such settings exist) to allow practicing against those moves?
But, unless you're seriously good can't you get the repetitive practice easily with engines?
That's a problem everyone has :)