In my long programming career I feel I did most of my programming nonverbally - large programs always felt I was sculpting a big chunk of stone rather than writing an essay.
Once it was done, I had no problem describing it, discussing it, documenting it, etc. But the actual task of programming felt like it was going on the non-verbal part of my brain.
These were mostly big programs, by the way: hard-real-time, or machine control, or threaded C++, or scientific data processing.
I found my style to be generally incompatible with pair-programming - except for pair debugging once my or someone else's code was written, that I did find useful.
In my long programming career I feel I did most of my programming nonverbally - large programs always felt I was sculpting a big chunk of stone rather than writing an essay.
Once it was done, I had no problem describing it, discussing it, documenting it, etc. But the actual task of programming felt like it was going on the non-verbal part of my brain.
These were mostly big programs, by the way: hard-real-time, or machine control, or threaded C++, or scientific data processing.
I found my style to be generally incompatible with pair-programming - except for pair debugging once my or someone else's code was written, that I did find useful.