Comment by freehorse

It is one thing to get code explained to you (which can also be good) but another to engage in finding a solution, explore the problem space, fail a couple of times and learn from your mistakes also, and of course the embodied process itself of writing the code. Learning is an active process; having stuff explained to you is not bad but it does not lead to the same depth of understanding. Granted, not all subjects and cases benefit the same from deeper understanding and it is impossible to get into depth with everything. So this is a trade-off in each case to decide how much one may want to go in, and it is great that we also now have this option to not go in the same depth. But imo one should be mindful about it, and make conscious decisions on how they use LLMs in case where they may think that understanding a subject more is also important.

There are still ways that LLMs can be used in that case, eg having them review your code, suggest alternatives to your code, eg more idiomatic ways to do sth, when you delve into sth new etc, and treat their output critically of course, but actually writing one's code is important for some kinds of understanding.