This is actually just how I learn. I never understand anything abstract the first time I read about it or use it. In fact there were many things in software tha

This is actually just how I learn. I never understand anything abstract the first time I read about it or use it. In fact there were many things in software that I just did because it was "best practices" without understanding why. I could read about the Why all day long but until I experience the Why it will never really click for me. I eventually understood why because I kept trying things out, asking questions, and didn't give up. I don't think you can expect most juniors to understand the Why to a lot of the things they are doing and one could argue that there isn't much value in ensuring they understand it right away. What matters is that you have processes in place to allow juniors to slowly learn why we do things the way we do. Seniors need to also understand that not everyone comes from a CS background nor is it necessary to come from one and be an effective worker. The work that 90% of programmers do out there is not complicated and anyone with a rudimentary understanding of algebra could do it.