Ask HN: How do you explain code verbally?
I find communicating code projects verbally weird. Any code of reasonable complexity in my opinion is much better communicated via detailed and well structured text documentation.
But compounding my issues is the fact I'm autistic and think about everything visually - this includes code which seems to take visual forms in my head. I don't know how to explain it, but I don't think with language and when communicating generally I feel as if I have to run my thoughts through a clunky mental transpiler.
I'd really like to be able to host great screenshare sessions where I can go through projects and explain things in a way which is clear and concise, but it seems no matter how hard I try, I can't do it.
I think I could do better if I had a lot of time to prep. This way I could create documentation with a mixture of text and imagery and go through that instead. But this isn't always possible.
I know some of you out there are verbally gifted, and I envy you, but for those of you who are not, have you been able to improve your ability to verbally communicate complex systems? Specifically, I'd appreciate hearing any strategies or processes you implement which improve your ability to communicate.