Write for One Person

wizardzines.com

111 points by evakhoury 2 days ago


Syzygies - an hour ago

I've spoken before a thousand several times saying with a straight face "Every audience is an audience of one."

My first example, I was asked to give one more talk on how one needs to shuffle seven times. There were four people, and a blackboard smaller than my kitchen window. I went for it like I was in office hours, which I've always enjoyed more than teaching. A few weeks later a phone call "I liked your talk." "Thank you." "Could you come to Switzerland to give it again? We can only offer a week's full expenses..."

Then I was asked to write a review of the off-broadway play "Proof" for the American Mathematical Society Notices. I didn't read it much, but I was told people do. I worked a very hard week on my review; my Swarthmore College classmate Ben Brantley's Broadway reviews were life or death for productions at the time, and I didn't want to embarrass myself. Ron Howard read my review, went to see "Proof" twice and loved it, and hired me to be the math consultant for "A Beautiful Mind". That was a transformative experience.

Every audience is indeed an audience of one.

https://www.ams.org/notices/200009/rev-bayer.pdf

GarnetFloride - 2 hours ago

I never try to speak to everyone as a tech writer. Tutorials are for people who'd never used our software before, but even then I could assume a certain level of computer literacy, for example they can launch out software or browse to a URL.

I can make How-to's that can assume they had gone through at least one of the tutorials, but even then I put links to the appropriate tutorials so they could refresh or learn if they needed it.

But lately it seems like people are getting more computer illiterate. So how low do you go? I am getting tempted to add a link to some basic computer literacy.

It's kinda like people complaining about Space Launch System, why aren't we using Saturn V or an improved version of it. We have the blueprints and schematics and everything but it appears there's a gap between what's written down there and what's in the textbooks. A lot of in-between experience has evaporated because shop classes and manufacturing were shut down.

I am realizing that a lot of experience was never written down and turned into institutional knowledge that could be used later. The AI companies would love this but it's gone because it was more cost-effective not to.

matheusmoreira - 2 hours ago

> Often this person is me

I wrote an article that never fails to put a smile on my face every time I read it. I felt like I had finally found my own voice. Ran it through Claude and it told me to tone it down a bit, but I ignored the advice and published it anyway.

The article caused people on HN to say I had issues. They weren't exactly wrong, but still. Be careful with what you publish out there. Warm reception is never guaranteed. My one consolation is the fact Bob Nystrom apparently liked it.

Jap2-0 - an hour ago

This reminds me of some comments by C.S. Lewis (paraphrasing from memory) on three ways of writing for children, two good and one bad:

- Writing for a specific child (think telling a story to someone specific)

- Writing because you have something to say and a story is how you want to say it

- Writing generally what you think a group of people want (e.g. "children like food so I'm writing a story about food")

I think the essay is available online, he is much more eloquent than I

neilv - 30 minutes ago

Hypertext to the rescue! Here's the lede sentence:

> In [Structured Query Language (SQL)](https://example.com/sql/), you can solve Unusual Complicated Problem with Super Advanced Thing.

That said, one time I had in mind a reader archetype, for whom I added an appendix of one basic concept, which ideally they'd already know, but likely didn't.

<https://docs.racket-lang.org/roomba/index.html#%28part._.Ass...>

I could've linked the some mentions of "association list" to a chapter of some textbook they'd never seen before-- and maybe they would read it, and maybe they would come back.

But instead, I decided to give a quick overview, in terms of an example relevant to what I was documenting, and leave them with a code pattern they could use, to get on with programming a robot like they came to my document to do.

(Though I wish I'd put an accessible showing-off demo example near the beginning of the document. After the intro, it reads a little too much like the glorified inline API docs that it is.)

PyWoody - 2 hours ago

Write to please just one person. If you open a window and make love to the world, so to speak, your story will get pneumonia

  - Kurt Vonnegut
thedreammachine - 30 minutes ago

Yeah, this is similar to finding 10 customers who love your software rather than 1,000 who only kinda like it. And if you do, it's probably because you've found a use case that is urgent enough for one specific kind of user.

throwaway7783 - 21 minutes ago

a.k.a the vaunted "Ideal Customer Profile". This is really critical for many many things in business and life.

ta2112 - an hour ago

Seriously! Every music theory blog post and video is like this. They're going to explain something like modes or maybe altered dominant scales, and they start out explaining intervals. Seriously stop, not from the beginning again! That's not your audience.

Multiplayer - 2 hours ago

I get stuck when I try to post on social and my brain fills up with all the random people I know that have commented or complimented a post. The problem is there are wildly different expectations of what I post. Is anyone else dealing with this?

Lately I've decided to write for ME. What do I want to write about? That has made it a lot easier to get unstuck. That and not looking at the views, likes, etc.

mproud - 2 hours ago

And for that matter, /developing/ for one person, often yourself, is probably better than for everyone. I’ll see this with app developers when they’re trying to figure out what kind of app or game to make. Just make the thing you would use!

simonw - an hour ago

Writing for "you, but three years ago" is excellent advice.

ergocoder - 37 minutes ago

I tried applying the same principle for building a product.

Then, I have a few products that have maybe 10 users.

Too niche is an issue.

samamou - 2 hours ago

wizardzines.com is one of the few things I am subscribed to by email <3