Isn't this the essence of teddy-bear/rubber-duck debugging? You're forcing yourself to run your abstract concepts through the narrow channel of language and i

Isn't this the essence of teddy-bear/rubber-duck debugging? You're forcing yourself to run your abstract concepts through the narrow channel of language and instantiating it in a way you haven't previously done (because if you had, you'd have solved the problem already and wouldn't need to be talking it through.) (I'm very specifically talking about the case where you explain and noone else contributes/responds, and you come up with the answer solely through trying to explain/speak it.)