"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
-
Show this thread
-
I also think that "You're not trying to write for X." is something that folks should be more comfortable with. Something that comes up occasionally: "I think you used a metaphor that a non-engineer wouldn't get." "That is likely accurate." "So you shouldn't do that." "Depends!"
3 replies 0 retweets 17 likesShow this thread -
Replying to @patio11 @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).
1 reply 0 retweets 1 like
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.
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.