[aedron]

Verbalizing your thought process is invaluable for validating that what you are doing/thinking actually makes sense. For developers, just think about all the times you have started explaining some code problem to a colleague, and instantly come upon the solution, simply by verbalizing ideas. The other person doesn't even have to say anything. There is even the concept of 'rubberduck debugging', where you explain things to a rubber duck, and it helps solve the problem.

I have often thought about what the experience would be of living entirely without verbalized thoughts. Like, obviously ideas and concepts exist separately from their verbal representations, so skipping words would be a more pure and effective form of thinking, right? But lately I have come to the belief that words are a necessary scaffold for organizing more complex ideas. Without them, I think we would simply be unable to put together complex enough models to understand things at the level we need to function in our complicated world. Like making diagrams helps with analysing domains.

It is proven that lack of verbal stimulation leads to slower develoment in children, possibly for the same reason. I think it is also the mechanism by which people who spend a lot of time alone (think castaways) eventually go insane - due to the lack of an external validation mechanism.

This understanding would seem to indicate that people who don't have an internal monologue would be less capable of expressing/understanding complex ideas. I would be very interested in knowing if that is the case.

[meeton]

So I'm one of these seemingly non-verbal thinkers, including when I code.

I think it makes me more capable of _making use of_ complex concepts. I came into programming through mathematics, and I treat them both as aesthetic exercises. When I'm building a system in my head the solution usually appears visually, and ideas overlay themselves over the problem as aesthetic "feels". Yes it's a lot like being a visual designer: I can step back, view the solution, and just 'see' if it looks right.

Why should we structure our solution like this? I can't easily put it into words but it just... would be more natural like this. And then a few days later the reason it was correct becomes liminal and I can explain it properly. It lets me hold more ideas in my head and make use of them all at once. When picking up a new idea I can grasp the underlying concept, see the symmetry with ideas I already understand, and slot it into place.

Of course it has major downsides too. It's an effort for me to put my full ideas into words. Coding, like anything worth doing, is a team sport. If I can't vocalize my ideas then half the time that makes them worthless, especially when the decisions are important and therefore contested. I tend to make mental jumps that lose other people, and lose track of what state other people have.

Also, and this is in line with what you said Aedron, it does make it harder to check the details. I'll make silly mistakes because checking them isn't part of my mental construct. I can chase a half-formed idea for a day before realizing my mental picture was off, and I didn't catch it because I never put the problem into words. Pracical-but-ugly hacks don't occur to me because they aren't aesthetic. I'm worthless at remembering my girlfriend's friends' names.

This year I'm focusing on moving slower, writing more things down, and talking to people more. So far it's been really helpful. But I don't think I'd have got to where I am now, or be able to solve the kinds of problems I do, if I was a mostly verbal thinker.