Writing at work
lcamtuf.substack.com
lcamtuf.substack.com
Seems like the only way I discover errors in my emails is AFTER I hit the SEND button. It's shocking how many errors I find in emails no matter how many times I proofread them.
I note that it specifically mentions being a window for edits prior to the comments going out in RSS feeds, and not intended explicitly as a deletion window, so it's still probably best not to make posts and then delete them (I used to have a pretty bad habit about it until the mods reached out).
The alternative is leaving posts in eternal draft mode while I sweat over the details. I find putting them live and editing-in-production makes me much more likely to actually publish!
I, somehow, taught myself to "read aloud in my head". That is, I can go back and read the text I've written as if I were speaking it aloud. It requires a slower, more deliberate reading of the text and I've noticed that my tongue is trying to move inside my mouth. So I assume I've somehow lit up areas of my brain that would be involved in actual speaking.
This is incredibly helpful to do because it enables you to re-read something almost as if you were someone else. The careful reader in you is very different from the writer.
Writing is very important for getting things done, communicating what you want and mean, and generally helping your work have visibility beyond your commit msg and code review.
These courses can be accomplished in a pair of weekends or a couple lunch breaks.