veyepar: Writer, Meet Tester

Author(s):	Arthur Louie, Jody Bleyle
Location	Crystal Ballroom
Date	may Mon 18	Days Raw Files
Start	10:10	First Raw Start	09:57
Duration	00:30:00	Offset	0:12:07
End	10:40	Last Raw End	10:40
Chapters	00:00
Total cuts_time	28 min.

http://lanyrd.com/2015/writethedocs/sdmwxp/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Writer_Meet_Tester.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

A software tester can be a tech writer’s best friend, and vice versa. Jody (writer) and Arthur (tester) work together on APIs at Salesforce.com, and we’ll talk about the tools and techniques we use to improve the quality of both our software and our documentation at the same time.
While our APIs are still in development, we gather feedback internally. We established an API design review board to approve every API change -- this made a huge difference in ensuring that we offer a consistent, easy-to-consume programmatic interface to our users. We also conduct regular “dogfooding” sessions in which users are provided with draft documentation and asked to find both doc and product bugs.
Our testers created an automated mechanism to alert us of any API changes in case anything slipped past the review board. It’s proven to be invaluable for both doc and testing to keep up with the various teams who are building functionality into the API.
Once our APIs are publicly available, we take pride in listening to our users in help forums, on Twitter, and through pilot programs. We’ve clarified our documentation and added test cases numerous times based on customer pain points.

Comment:

production notes