There's a quote out there that I can't find, but it says something along the lines of a senior engineer's job is to make more senior engineers. The same is true of anyone in a leadership position. Their function is to influence and guide individuals and groups to make the group stronger and better. Even if it's not formally in their job description, if they are truly a leader and not just a manager, part of their duty and responsibility is to make the team better, and one way to do this is to increase the knowledge of the team.
Coming from a software engineering background, I'd expect anyone with any amount of education in the field to understand avoiding magic numbers, preferring well-named variables or constants. It's not something that I'd expect to have to explain. However, I'd also hope that the work environment is safe enough where a very junior member would be able to ask and receive an explanation.
Not every statement needs to be explained. If it's something that could be considered a best practice, good practice, or common knowledge, I wouldn't expect to need to explain it. However, I'd be open to turning anything into a teaching moment. Depending on what it is, perhaps the more junior person can teach the more senior person. The most important thing is a safe environment for teaching and learning, where questions can be asked.