veyepar: A Developers Approach to Documentation: From Passive to Dynamic

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:	The era of O’Reilly books is done, finito, kaput. With so much of the developer experience online, we know a great deal about each individual user and about the code we document. Why, then, do we documentarians persist in providing the same walls of text to each of our readers, especially when there are so many more personalized ways of describing technical tools and code? This talk addresses the move from passive to dynamic documentation. As code goes mainstream, more and more consumers of APIs and technical writing will be non-technical. Technical writing bears a responsibility to reduce the learning curve as much as possible for these readers, and it can do that by being much more intimate about its relationship with them. markdown
Comment:	production notes

2015-05-18/13_45_04.dv Apply: 13:51:51 - 14:20:19 ( 00:28:28 ) S: 13:45:04 - E: 14:20:19 D: 00:35:15 (Start: 6:47) show more...

vlc ~/Videos/veyepar/eric/wtd_na_2015/dv/crystal_ballroom/2015-05-18/13_45_04.dv :start-time=0407.0 --audio-desync=0

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this