"You're not trying to write copy for people who don't have time for you. That is never going to work out." You make copy scannable to conserve attention & cause people to remember important parts, not to have them not read the parts between the bold bits. #microconf @copyhackers
-
-
Caveat: what you think engineers know often isn't true. For some Bitbucket Server copy, I did a informal survey of coworkers to find out what they thought "fast-forward merge" means in Git. Nobody out of 6 got it right (incl. Architects, Sr Devs, Jr Devs).
-
Yeah, people usually mention this to me in the context of using something like "for loop", which is a) impenetrable jargon for 99% of humanity and b) absolutely table stakes for developers.
End of conversation
New conversation -
-
-
I showed my wife a tweet of yours, she asked me what half the words meant and was unsure if some of the words were even English.
-
One of my picoheresies: I'm pretty cool with this result. The Internet rounds to infinitely large and there is something on it for everyone, so my writing doesn't have to be everything for everyone.
- 2 more replies
New conversation -
-
-
I think a lot more documents need to be written with an implicit acceptance of assumed knowledge. If the reader doesn’t already know A,B, or C they’re not going to convert/whatever. Explaining those items to the rest of your audience just bogs them down.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.