veyepar: TechDocs at Twitter: Creating the Culture of Documentation

Author(s):	Simeon Franklin, Marko Gargenta
Location	Crystal Ballroom
Date	may Mon 05	Days Raw Files
Start	15:50	First Raw Start	15:57
Duration	00:40:00	Offset	0:07:40
End	16:30	Last Raw End	16:37
Chapters	00:00 0:29:54
Total cuts_time	36 min.

http://conf.writethedocs.org/19
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf TechDocs_at_Twitter_Creating_the_Culture_of_Documentation.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

Twitter Engineering has grown quickly, to well over a thousand engineers in the space of a few years. In the process, scores of teams have developed hundreds of individual services and libraries. During this time, these teams have been supported by at most three fulltime tech writers.

This is a story of how we work towards creating the culture of documentation. To implement this culture, we needed to introduce new tools that are seamless for the developer workflow and to bring the teams along with education and training. In this talk, you will learn what worked and what didn’t for Twitter engineering documentation.

Twitter is a large organization with many projects, a variety of languages, and wildly varying standards for documentation. This talk shares the experiences of our newly formed university engineering education division.

* Building and distributing documentation tools for a large in-house technical audience
* Evangelizing for broader developer participation in documentation
* Using rewards, policies, metrics, and public shame to drive documentation quality

Comment:

production notes