Improving the Signal in Public Technical Writing
Writing about technical topics in public often invites a mix of useful corrections, thoughtful additions, and the occasional unpleasant comment. One common piece of advice is to ignore the comments entirely, but that would mean missing out on a wealth of shared experience and knowledge. A more productive approach is to shape the conversation itself, steering it toward the kinds of comments that add value.
Stick to Verifiable Claims and Stories
Focusing on facts about how systems behave, rather than subjective preferences, naturally attracts fact-based responses. A post about a tool like tcpdump tends to generate comments that are concrete: people share their own use cases, point to alternative resources, mention related flags or utilities, and flag potential pitfalls. These are precisely the comments that are most informative.
Even simple stories about debugging a problem are valuable. They invite readers to share whether they have encountered the same issue, suggest alternative solutions, and explain how the problem fits into a broader context. Stories about hard-won debugging sessions also serve a practical purpose: they can be the resource that helps someone else solve the same problem later.
Ask Questions and Invite Specific Feedback
Explicitly stating where your knowledge ends—either by asking a question or noting that you are unsure about something—focuses discussion. People enjoy answering questions, and this creates a situation where both sides benefit. The commenter gets to demonstrate expertise, and you get an answer to a genuine gap in your understanding.
Mistakes are inevitable when writing at the edge of your knowledge. The best response is to fix them quickly after publishing. Staying near a computer for a few hours after posting makes it easy to incorporate corrections as they arrive. Maintaining a detailed errata log is not necessary; simply editing the post to remove the error is sufficient.
Request Experiences, Not Just Opinions
Opinions, such as "this web interface is bad," often lead to unproductive debates. Asking for a specific experience—like "which DNS record types have you needed to manage?"—yields richer information. People can describe the concrete situation that led to their preference, which is more informative than a general stance. It is worth modeling this behavior in your own comments by explaining the experiences that shaped your opinions. A specific question like asking about TLSA records after a vague complaint can reveal that certain record types are often unsupported in common tools, which is a genuinely useful piece of knowledge.
Provide Context and Preempt Boring Debates
Comments often go sideways when readers have no idea why you are writing about a subject. A brief note on your background or the reason for the post—such as a recent migration to a new operating system or a specific project that prompted the research—gives readers helpful framing and reduces misconceptions.
Some conversations are predictable and tedious. Topics like language wars, editor preferences, and a handful of other perennial flamebait triggers often lead to repetitive arguments. It is usually best to avoid writing about these unless you have something genuinely new to say. Even in normally dull areas, specific and technical angles can still spark interesting discussion.
It is also wise to preempt obvious suggestions that you have already considered. A short note explaining why you chose not to use a particular tool or approach—for example, listing a set of features you are deliberately avoiding and why—prevents a flood of "you should use X" comments. This also helps readers who may be unaware of those options.
Set Boundaries and Ignore Arguments
Occasionally, commenters cross a line. When this happens on platforms where you control your audience, blocking or calling out unacceptable behavior can be necessary to maintain a healthy space for discussion. This may drive away some people, but it is often worth it. On platforms without such moderation tools, this is not an option.
There is little to be gained from engaging in arguments with dismissive commenters. Not replying, even when they are wrong, is often the most productive strategy.
Learn From Unpleasant Feedback
Unexpectedly negative comments can still contain useful lessons. If a post about a toy DNS resolver drew criticism for not handling packet parsing, it might seem unreasonable at first. But the underlying message could be that the parsing step was not as clear to readers as it was to you. That kind of feedback can inspire a future post that focuses more heavily on the area readers found confusing, ultimately producing a better resource for everyone.
Finding something useful in criticism does not mean being immune to it. Even when it stings, analyzing the comments to extract a takeaway can be a coping mechanism that leads to improvement.
