From Karl Sutt’s post How to communicate effectively as a developer, two images:
The images on the left are what Karl calls “low resolution” writing, while the right is “high resolution.” Pretty obvious when you look at it here, but high resolution essentially means more specific, detailed, and includes necessary calls to action. It’s extremely easy, in the context of something like Slack, to be low resolution. Watch for it!
I like Karl’s post in part because you might hear people ([cough], like me, regularly) talk about the importance of writing. I rarely say it, but I mean any writing. Not just stuff like documentation, emails, and blog posts, but short-form and often casual writing as well, like Slack and GitHub comments.
Leave a Reply