[sedatk]

What an insighftul analysis. I haven't noticed how vague my writing was until I started writing my book. Editors had to constantly correct me on missing information in my sentences which I didn't notice beforehand even once. They were always right. The whole writing experience has been truly eye-opening for me about how teaching is an entirely different skill set than writing.

[2muchcoffeeman]

This is why it’s valuable to proof read your work. After you write it, come back the next day and see if you still like it or it makes sense.

[MrVandemar]

Not just proof read it, but read every word out loud. You'll pick up mistakes, awkward sentence structure, poor word choices that you never would by reading it silently. Reading alound means you don't skim.

[makapuf]

Yes for superficial structure, I might skip things reading silently. However I struggle to think about the meaning of what I read when I read aloud, different focuses maybe. So that's complimentary.

[codyb]

Precision and brevity are my guides for code comments after a careful ux analysis of comment encounters in code.

Anything that makes me pause while reading code or a comment is something I’ll strive in a timeboxed manner to simplify.

It’s not always possible, but my code doesn’t get a lot of style comments or comments about readability anymore so seems to be working.

[hackerfromthefu]

The difference may be that you are not getting feedback on the quality of your teaching.