Twitter | Search | |
Search Refresh
Bob Watson, PhD Aug 1
That’s a novel approach to tech docs.
Reply Retweet Like
Bob Watson, PhD Aug 17
Found this post on "generating" API documentation, which got me thinking about the verb(s) developers use to describe documentation authoring vs. the verbs(s) uses to and what that means.
Reply Retweet Like
Bob Watson, PhD Aug 2
[With] "bad survey questions, you get bad data at scale with no chance of recovery." A short, but valuable, must read for anyone contemplating a survey.
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
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 Oct 21
Ouch! Does this sound right to those in and who ?
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 Aug 27
This thread talks about a problem with having too narrow of a focus. It’s easy to show action, but do you make actual progress? I’ve seen where these observations apply to the that supports these projects, as well.
Reply Retweet Like
Bob Watson, PhD Sep 10
This photo captures so many cool aspects about * Amazing audience * Great speakers * Interesting topics * Live captioning * Live streaming * Live tweets
Reply Retweet Like
Bob Watson, PhD Jul 24
So, what can we call documentation for a similar effect? Most of the reader's goals WRT documentation also occur offline. Solutions? Success Augmentation? Whachagot ?
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 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 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
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 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 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 6
Replying to @reb_yoel
That makes more sense. The challenge with doc feedback is nobody (but and folks) think about 'em until they need 'em. It's a rare and delicate moment because they think about 'em just long enough to not have to think about 'em anymore.
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