TY  - GEN
N2  - Learn to integrate programming with good documentation. This book teaches you the craft of documentation for each step in the software development lifecycle, from understanding your users needs to publishing, measuring, and maintaining useful developer documentation. Well-documented projects save time for both developers on the project and users of the software. Projects without adequate documentation suffer from poor developer productivity, project scalability, user adoption, and accessibility. In short: bad documentation kills projects. Docs for Developers demystifies the process of creating great developer documentation, following a team of software developers as they work to launch a new product. At each step along the way, you learn through examples, templates, and principles how to create, measure, and maintain documentationtools you can adapt to the needs of your own organization. You will: Create friction logs and perform user research to understand your users frustrations Research, draft, and write different kinds of documentation, including READMEs, API documentation, tutorials, conceptual content, and release notes Publish and maintain documentation alongside regular code releases Measure the success of the content you create through analytics and user feedback Organize larger sets of documentation to help users find the right information at the right time.
DO  - 10.1007/978-1-4842-7217-6
DO  - doi
AB  - Learn to integrate programming with good documentation. This book teaches you the craft of documentation for each step in the software development lifecycle, from understanding your users needs to publishing, measuring, and maintaining useful developer documentation. Well-documented projects save time for both developers on the project and users of the software. Projects without adequate documentation suffer from poor developer productivity, project scalability, user adoption, and accessibility. In short: bad documentation kills projects. Docs for Developers demystifies the process of creating great developer documentation, following a team of software developers as they work to launch a new product. At each step along the way, you learn through examples, templates, and principles how to create, measure, and maintain documentationtools you can adapt to the needs of your own organization. You will: Create friction logs and perform user research to understand your users frustrations Research, draft, and write different kinds of documentation, including READMEs, API documentation, tutorials, conceptual content, and release notes Publish and maintain documentation alongside regular code releases Measure the success of the content you create through analytics and user feedback Organize larger sets of documentation to help users find the right information at the right time.
T1  - Docs for developers :an engineer's field guide to technical writing /
DA  - 2021.
CY  - [Place of publication not identified] :
AU  - Bhatti, Jared,
AU  - Corleissen, Zachary Sarah,
AU  - Lambourne, Jen,
AU  - Nunez, David,
AU  - Waterhouse, Heidi,
CN  - T11
PB  - Apress,
PP  - [Place of publication not identified] :
PY  - 2021.
ID  - 1440142
KW  - Technical writing
KW  - Rédaction technique
SN  - 9781484272176
SN  - 148427217X
TI  - Docs for developers :an engineer's field guide to technical writing /
LK  - https://univsouthin.idm.oclc.org/login?url=https://link.springer.com/10.1007/978-1-4842-7217-6
UR  - https://univsouthin.idm.oclc.org/login?url=https://link.springer.com/10.1007/978-1-4842-7217-6
ER  -