Twitter | Search | |
Search Refresh
Bob Watson, PhD Dec 8
Content that shows they know their audience.
Reply Retweet Like
Bob Watson, PhD 16h
Great list of talks at this year’s east conference. Bummer that I can’t be there. You’ll just have to enjoy it double (which should be easy!).
Reply Retweet Like
Bob Watson, PhD Jul 3
“If your boss is asking you to quantify the value of your work, you need to understand that your work indeed has no value. Not at that company. Not with that boss.” Applies to , too.
Reply Retweet Like
Bob Watson, PhD Jun 25
If wants to usability test their documentation, here are some tips for setting up a testing space. It doesn’t have to be complicated or expensive.
Reply Retweet Like
Bob Watson, PhD Jun 17
I love it when documentation is part of the design & code.
Reply Retweet Like
Bob Watson, PhD Jun 13
I love it when devs talk about documentation. needs to be alert for these moments to: - help answer their questions - share tips and tricks - meet allies for future conversations - learn more about their audience
Reply Retweet Like
Bob Watson, PhD Jun 9
“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” — Martin Fowler Maybe there’s an opportunity for to help devs write more readable code?
Reply Retweet Like
Bob Watson, PhD May 12
Finally had a chance to reflect on the PDX conference. In a few days, I’ll work up the nerve to watch the video of my talk and see what I can learn for next time.
Reply Retweet Like
Bob Watson, PhD May 9
While I was able to attend this year, I want to thank all the prolific tweeters for their efforts and tell them I’ve appreciated their work in the past when I’ve not been able to attend
Reply Retweet Like
Bob Watson, PhD May 8
The secret is out now! Had a great time at in PDX! What a great group of documentarians!!
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
Amber Matz May 8
I love this description of 3 potential preferred coding styles of your API’s audience by
Reply Retweet Like
Bob Watson, PhD Mar 12
Reviewing your GitHub account seems to be the CV equivalent of "just read the code" for documentation. Sure it might work, but there are more efficient ways to communicate with the audience.
Reply Retweet Like
Bob Watson, PhD Mar 2
And please include quality documentation in your budget. You can thank me later.
Reply Retweet Like
Bob Watson, PhD Mar 1
The same ratio applies to the code's documentation, too.
Reply Retweet Like
Bob Watson, PhD Feb 26
My new favorite site: Best practice articles with references to the source research from which the best practices are derived. I'm in TC research geek heaven!
Reply Retweet Like
Bob Watson, PhD Feb 26
An interesting topic for , does your content need to be read quickly or slowly? (hint, not all content is alike)
Reply Retweet Like
Bob Watson, PhD Feb 20
I'm not a fan of using ROI for , but this is a great article about using the need to demonstrate ROI as a reason to develop meaningful measurements and benchmarks (and they cited references!)
Reply Retweet Like
Bob Watson, PhD Feb 14
A great lineup of speakers await you at this year's conference in PDX (even if I do say so myself)
Reply Retweet Like
Bob Watson, PhD Feb 3
I love it when I find an article on content metrics that makes me smile. provides advice that even should heed. Love the quote from Mike Powers: "Pageviews aren’t the goal. Your goal is the goal."
Reply Retweet Like