Twitter | Search | |
Search Refresh
Stoplight May 8
What problems do users want to solve: - System or task-oriented problems
Reply Retweet Like
Lisa Tagliaferri May 8
How an API matches the audience's problem and skills determines how much you'll work on documentation
Reply Retweet Like
Stoplight May 8
How they solve problems like their preferred coding styes, examples: - Copy and paste code and hope for the best - Try first and fix it by reading the docs - Study the docs and apply the code
Reply Retweet Like
Documentation Demon Sep 14
Replying to @bobwatsonphd
just came here to say "by catch you don't mean broadcast on twitter?" Well preempted.
Reply Retweet Like
David Smatlak May 8
Fantastic presentation about API docs!
Reply Retweet Like
Lisa Tagliaferri May 8
Important to know how your users are using an API — what problems are they trying to solve? — when writing API documentation
Reply Retweet Like
Lisa Tagliaferri May 8
Develop your API documentation plan based on Audience Market Product Strategize and develop / refine plan, prioritize by content type
Reply Retweet Like
Bob Watson, PhD Sep 9
Well, I might as well just admit it. I'm not going to get much done as long as the live tweets are coming out of the conference.
Reply Retweet Like
Mike Jang Aug 7
Replying to @bobwatsonphd @Google
Thanks Bob! I think the study focuses on what Devs search for in code (only implicitly how we can modify docs to meet these needs)
Reply Retweet Like
Bob Watson, PhD Aug 1
That’s a novel approach to tech docs.
Reply Retweet Like
Catherine Heath 💫 May 8
Learning about API documentation with who advises use to use our audience, product and market to determine what we write. You build momentum with these things and thus create successful documentation.
Reply Retweet Like
Stoplight May 8
How to determine how much you will need to write based on your audience's tendencies
Reply Retweet Like
Bob Watson, PhD Aug 27
Good things for to keep in mind when communicating the value of APIs to a broader audience.
Reply Retweet Like
Bob Watson, PhD Mar 1
The same ratio applies to the code's documentation, too.
Reply Retweet Like
Bob Watson, PhD Aug 20
So far, I've found 114 articles on API documentation and I'm thinking of organizing them for a study. I'm wondering what aspects , , and think might be interesting? I started by target audience.
Reply Retweet Like
Bob Watson, PhD Jun 17
I wonder if saying, “I don’t know” would make the answers tech gives more credible or make the tech seem less trustworthy?
Reply Retweet Like
Bob Watson, PhD Aug 1
Fascinating research. Talk about getting to know your audience!
Reply Retweet Like
Bob Watson, PhD Aug 4
Interesting observations coming out of , this weekend...
Reply Retweet Like
Bob Watson, PhD Dec 11
Replying to @bobwatsonphd
I used to be in that target audience, so I recognize the message. The challenge for those in who is to know what their readers need from the docs to help them achieve their success. Basically, know your audience with precision.
Reply Retweet Like
Jay Elmore May 8
So starts off the final talk by telling everyone what we all came to learn...
Reply Retweet Like