LEADER 03453nam 22005895 450 001 9910502623803321 005 20240617214308.0 010 $a9781484272176 010 $a148427217X 024 7 $a10.1007/978-1-4842-7217-6 035 $a(CKB)4100000012038123 035 $a(MiAaPQ)EBC6738529 035 $a(Au-PeEL)EBL6738529 035 $a(OCoLC)1273075345 035 $a(DE-He213)978-1-4842-7217-6 035 $a(CaSebORM)9781484272176 035 $a(PPN)258057785 035 $a(Perlego)4513546 035 $a(EXLCZ)994100000012038123 100 $a20210930d2021 u| 0 101 0 $aeng 135 $aurcnu|||||||| 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 10$aDocs for Developers $eAn Engineer?s Field Guide to Technical Writing /$fby Jared Bhatti, Sarah Corleissen, Jen Lambourne, David Nunez, Heidi Waterhouse 205 $a1st ed. 2021. 210 1$aBerkeley, CA :$cApress :$cImprint: Apress,$d2021. 215 $a1 online resource (241 pages) 311 08$a9781484272169 311 08$a1484272161 320 $aIncludes bibliographical references and index. 327 $a1. Getting Started -- 2. Researching Documentation -- 3. Designing Documentation -- 4. Drafting Documentation -- 5. Structuring Sets of Documentation -- 6. Integrating Code Samples and Visual Content -- 7. Measuring Documentation Success -- 8. Working With Contributors -- 9. Maintaining Documentation -- 10. Wrapping Up. 330 $aLearn 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 documentation?tools 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. 606 $aInternet programming 606 $aOpen source software 606 $aWeb Development 606 $aOpen Source 615 0$aInternet programming. 615 0$aOpen source software. 615 14$aWeb Development. 615 24$aOpen Source. 676 $a005.15 700 $aBhatti$b Jared$01072868 702 $aHightower$b Kelsey 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910502623803321 996 $aDocs for developers$92890765 997 $aUNINA