It's worth to distinguish writing for yourself (to think) from communication.
Recently I discovered a lecture about technical writing in academics (from my "writing to think" folder: https://www.youtube.com/watch?v=vtIzMaLkCaM) that drove this point home: If you're an academic, your default mode of writing is "writing to think", and you have to make a conscious effort to avoid this mode when you communicate.
I think it also goes the other way: If you mostly write for others (or read what they write or say in public), then you need to make a conscious switch to "writing to think", which is a different skill where you worry less about being misunderstood and more about connecting to your personal knowledge.
Recently I discovered a lecture about technical writing in academics (from my "writing to think" folder: https://www.youtube.com/watch?v=vtIzMaLkCaM) that drove this point home: If you're an academic, your default mode of writing is "writing to think", and you have to make a conscious effort to avoid this mode when you communicate.
I think it also goes the other way: If you mostly write for others (or read what they write or say in public), then you need to make a conscious switch to "writing to think", which is a different skill where you worry less about being misunderstood and more about connecting to your personal knowledge.