This was a great read and conscious of the nuances to effective writing. Articles like these tend to have a "write this way NOT this other way" mentality. To pa

This was a great read and conscious of the nuances to effective writing. Articles like these tend to have a "write this way NOT this other way" mentality. To paraphrase a comment I saw somewhere regarding code optimization: "Given enough time most code can be optimized quite a lot". The same can be said about writing. The audience, the topic, and the intended outcome make for a complex optimization problem that, as the author touches on, can eat up a ton of time. The PR comment example is perfect. The initial comment (on the lefthand side) works. *It does the job*, however when the author is placed in a different context (audience and intent), the comment on the right becomes more optimal. It also took 5x the amount of time to write up. I feel as though knowing the tradeoffs and managing your own time seems to be half the battle when it comes to communicating. My additional advice for devs is; get honest feedback on your writing (slack messages, design documents and everything in between) so that you can learn best what works with whom.