Julia Evans' Wizard Zines released a new comic on writing for one person, challenging the common advice to write for everyone. The piece argues that addressing a single reader makes content more personal and effective, particularly in technical documentation. This approach helps writers avoid vague generalizations that often dilute their message.

Writing for one person simplifies the process by giving authors a clear audience in mind. Instead of guessing what thousands of readers might want, focusing on one individual creates more authentic and direct communication. For developers explaining code or documenting systems, this means choosing a specific teammate or colleague as their reference point.

The comic resonates because technical writing often suffers from abstraction. When engineers write for an imagined generic audience, the result frequently lacks the concrete examples and specific context that real readers need. Writing for one person forces specificity and relevance.

This advice applies broadly to documentation, README files, and code comments. Developers who adopt this mindset often find their explanations become clearer and more actionable, making technical knowledge more accessible to teammates and future maintainers.