When you learn when not to use it.
For me, the more interesting question is: what am I learning from this language. This tends to follow the inverse curve: I learn a lot early on, but a language's impact on my programming reduces over time. Learning a new paradigm obviously increases that much more that learning a fifth variant on a paradigm I've used for umpteen years.
Of course, different people have different motives. Some may want to be the best 3D programmer out there. That path looks different than my "I want to be an incredibly valuable, generalist programmer". My path let's me work on lots of different types of projects, but I'll never understand AI like Peter Norvig.
In the end, look at your real goals, keep track of your progress, and adjust course as necessary to keep moving in the direction you want.
Adapting that to technology one may build systems in say Java but never use particular built in classes, maybe they use the Apache classes instead. This is their style and so long as it produces quality results, it can be said that they are a master.