I've found that I can't talk at all. I record myself to track down any inefficiencies and I decided to talk during some sessions.
I miss words, I use wrong words. Sometimes I completely go silent when working out a tricky part.
My hypothesis is that the implementation part should be 2nd nature and I should be able to talk through it. So I'm probably switching from notepad to editor too quickly.
My language skill (as my "1st nature") completely sucks. I feel impossible to explain the solution any problem more than 2200 rated. Sometimes I try to explain something and end up messing it up. Don't know if your problem is same as mine.
I'd say explaining the solution is something I can do, once it finally works.
Of course, the explanation of solution does not mean I can explain how I got there. For some problems it can be a systemic mathematical symbolic manipulation. This symbolic manipulation can be hard to follow if I omit steps that are obvious to me, but if I really try to go step-by-step it is fine.
For other solutions it's like a rabbit-out-of-the-hat moment where I just come up with the invariant/approach that works.
But my problem is that while I'm problem solving, my internal thinking renders me incapable to talk coherently. I either talk like I'm having a brain stroke or I just use incorrect words. I feel that these attempts to talk about it also impact my ability to fully solve it.
I'd compare it to playing an instrument and singing at the same time. At least 1 thing needs to be 2nd nature and fully out of focus, so that I can do the other. This might imply I either don't know how to sing, or don't know how to really play the guitar, I'm working at a lower level and have to practice more to have the whole thing chunked.
For problem solving, it's like I still cannot just type out the solution that's compressed in my brain, or I am thinking consciously too much about the solution so I cannot talk about what I'm coding.
talking while coding = cheat!!
Do you mean when you code the solution or when trying to figure it out? I don't know exactly why would you need to talk while coding a solution? I might leave some comments regarding how tuples are used or if there are very many big steps I might at times leave a short comment like "now search for X that has Y condition" so I don't end up forgetting to do that. When I think a solution I usually have a paper on hand + write in a .txt file (depends on how I'm viewing the problem, it's easier to draw a graph on paper) some ideas or some self-made samples to better understand the problem. However I'm not super sure how much this helps, I've started doing it somewhat recently.