48
8 Writing Tips for Software Professionals
(optimizedbyotto.com)
In this post, I share 8 principles I believe in:
- Less is more
- Start with the solution or the ask
- Show the facts, with examples
- Always quantify
- Include links and references
- Explain why it matters
- Ask feedback from one person
- Sleep on it
As engineers and developers, we often focus heavily on technical skills while neglecting the importance of clear, compelling writing. But the reality is, our ability to communicate effectively can have a major impact on our careers.
The last two points, "Ask feedback from one person", and "Sleep on it" I think are great. Ironically the article ignores the rest of its own tips.
Circular logic. Q: "how do I write more efficiently?" A: "with less words" This "tip" could be omitted entirely.
Better title: "8 Writing Efficiency Tips for Software Professionals", or maybe "8 Tips for Software Professionals to Communicate More Efficiently"?
No text extracts provided in the article. For example a rewritten paragraph, or comparison of some summaries.
Always! Except for this article which does not suggest a way to measure the efficiency of text e.g. number of words to convey the same message.
None provided.
Why would I want to write more efficiently? What real-world problems does efficient writing solve? Maybe I'm a software engineer new to the field and I don't know how pressed for time some managers are, or how people are drowning in verbose corporate junk words?
Maybe this article was LLM generated, like the cover graphic :(