TL;DR
The author offers guidance on writing complaints that persuade rather than alienate. Key tips: avoid absolute claims, prefer descriptive framing over contested names, provide context, and have a clear, constructive purpose.
What happened
A short essay published on March 25, 2024, lays out principles for crafting useful complaints and critique in technical writing. The piece warns against blunt, categorical statements and against relying on disputed terminology that can prompt defensive reactions from readers who use different names for the same things. Instead of declaring one thing universally superior to another, the author recommends describing the problem being solved and explaining why a particular approach avoids certain pitfalls. The essay also argues that background and framing are not mere repetition for knowledgeable readers but are necessary to set the terms of the argument and broaden accessibility. Finally, it urges writers to ensure a complaint has a legitimate purpose, to avoid dumping negativity into the world, and to temper tone with empathy when the goal is persuasion.
Why it matters
- Ambiguous or contested names can provoke defensive feedback and reduce the persuasive impact of criticism.
- Absolute claims raise the bar for justification and can be harder to defend than nuanced comparisons.
- Providing context and framing broadens who can understand your argument and reduces reliance on assumed knowledge.
- A complaint without a clear purpose or constructive intent risks adding unnecessary negativity rather than producing useful change.
Key facts
- The essay was published on March 25, 2024.
- Authors should prefer describing approaches and problems instead of relying on potentially disputed names.
- Absolute statements (e.g., 'X is always better than Y') are discouraged because they demand strong defenses.
- Framing the problem helps avoid readers' preconceptions and makes arguments accessible to a wider audience.
- Contextual descriptions can serve to set up an argument, not merely to define a term for readers who already know it.
- Writers are advised to ensure a complaint has a good reason to exist rather than merely expressing negativity.
- Using a less acerbic tone and showing empathy are recommended when the goal is to convince others.
What to watch next
- Reader pushback rooted in differing terminology — not confirmed in the source
- Whether framing complaints with context actually increases constructive engagement — not confirmed in the source
- If gentler tone and empathy lead to more agreement or productive discussion — not confirmed in the source
Quick glossary
- Framing: Presenting the context and boundaries of a problem so readers understand the specific perspective and criteria you are using.
- Absolute statement: A claim expressed as universally true or without exceptions (e.g., 'always' or 'never'), which typically requires strong evidence.
- Terminology: The set of names or labels used to refer to concepts; these can vary between communities and cause misunderstandings.
- Empathy: Considering and acknowledging others' perspectives and feelings when communicating, often to increase receptivity.
Reader FAQ
Should I avoid using technical names when criticizing something?
The source recommends reducing reliance on disputed names and instead describing the approach or problem to avoid alienating readers.
Is it okay to make strong claims like ‘X is always better than Y’?
The essay advises against absolute claims, noting they require disproportionately strong justification and are harder to defend.
Does adding background hurt knowledgeable readers?
No — the author argues that context helps frame the argument and can make the criticism accessible rather than merely repeating definitions.
When is a complaint worth publishing?
The piece says a complaint should have a good reason for existing and cautions against publishing negativity for its own sake.
How to complain 2024-03-25 A rare divergence from our regularly unscheduled computer junk brings you: computer people junk. Try to avoid writing things like this Foo is bad, and bar…
Sources
- How to Complain
- How To Give & Take Constructive Criticism | CLS
- How to Give and Receive Constructive Criticism
- Constructive Feedback and Criticism: A Practical Guide …
Related posts
- fcvvdp: a compact, high-performance C implementation of the CVVDP metric
- Best Japanese Learning Tools 2025: Winners Across Apps, Anki, and Readers
- Why I Disappeared: A Week Offline in the Galapagos Revealed News Noise