DaFranker comments on Looking for alteration suggestions for the official Sequences ebook - Less Wrong

13 Post author: alexvermeer 16 October 2012 10:32PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (73)

You are viewing a single comment's thread. Show more comments above.

Comment author: Dolores1984 16 October 2012 11:02:00PM *  20 points [-]

Oh, and somebody get Yudkowsky an editor. I love the sequences, but they aren't exactly short and to the point. Frankly, they ramble. Which is fine if you're just trying to get your thoughts out there, but people don't finish the majority of the books they pick up. You need something that's going to be snappy, interesting, and cater to a more typical attention span. Something maybe half the length we're looking at now. The more of it they get through, the more good you're doing.

EDIT: Oh! And the whole thing needs a full jargon palette-swap. There's a lot of LW-specific jargon that isn't helpful. In many cases, there's existing academic jargon that can take the place of the phrases Yudkowky uses. Aside from lending the whole thing a superficial-but-useful veneer of credibility, it'll make the academics happy, and make them less likely to make snide comments about your book in public fora. If you guys aren't already planning on a POD demand run, you really should. Ebooks are wonderful, but the bulk of the population is still humping dead trees around. An audiobook or podcast might be useful as well.

Comment author: DaFranker 17 October 2012 08:14:06PM 2 points [-]

Regarding the jargon, I agree with wedrifid that LW-specific jargon is actually being defined as the sequences, and from what I've heard and experienced this is extremely helpful in setting down a common language for us to discuss these matters.

However, there is some jargon that could and probably should be done away with: the computer science stuff. Not all sequences/articles have it, but when it's there it's usually several levels of inference away from laypeople. The CS/programming examples, comparisons and metaphors are fun for someone like me, but it's an accepted matter among IT people that things like the XKCD comic on a random function that always returns 4 will not help get the point across to non-IT people.

I'm sure that has been mentioned before, but it's worth making sure that it's looked over and that while doing it you remember that when writing educative material, most people severely overshoot the level that they're aiming for, and end up writing a text that's perfect for undergrads when they were targeting a middle school audience or somesuch.

Personally, I'd leave in most of the random intercultural references (like the anime references, for instance) since I suspect they'd still reach a good portion of the audience and wouldn't have negative impact, but that'd be up for discussion. This also gives me an idea, but I'll make a separate comment for it.

Comment author: Epiphany 20 October 2012 01:17:48AM *  1 point [-]

However, there is some jargon that could and probably should be done away with: the computer science stuff.

On the one hand, I agree with you. If people can't understand, then that's bad. On the other hand, touches like those give the sequences personality, and that personality may be part of what makes them popular.

Usually, though, there's a way to phrase IT descriptions such that everyone can understand. I do this for my boss all the time. Maybe giving it a high-tech "personality" and making it comprehensible are not mutually exclusive.

Comment author: DaFranker 22 October 2012 01:41:46PM 0 points [-]

Yes, I agree.

The IT culture stuff is good, what I think wouldn't pass is specific IT vocabulary or concepts that don't get introduced within the sequences and that is assumed to be understood.

I seem to recall a reference somewhere of object-level vs class-level distinctions, and someone who's never heard about OOP would have no idea that we're basically talking about the programming equivalent of specific emails vs email templates (or "an email", or whatever helps make them understand, but I've found the specifc email vs template example sufficient as a first step for most people I've had to explain this to).