| 000 | a | ||
|---|---|---|---|
| 999 |
_c30608 _d30608 |
||
| 008 | 220106b xxu||||| |||| 00| 0 eng d | ||
| 020 | _a9781484272169 | ||
| 082 |
_a808.066 _bBHA |
||
| 100 | _aBhatti, Jared | ||
| 245 | _aDocs for developers : an engineer’s field guide to technical writing | ||
| 260 |
_bApress, _c2021 _aNew York : |
||
| 300 |
_axxv, 225 p. ; _bill., _c24 cm |
||
| 365 |
_b34.99 _cEUR _d88.70 |
||
| 504 | _aIncludes bibliographical references and index. | ||
| 520 | _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. What You'll Learn 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 Who This Book Is For Ideal for software developers who need to create documentation alongside code, or for technical writers, developer advocates, product managers, and other technical roles that create and contribute to documentation for their products and services. | ||
| 650 | _aSoftware documentation | ||
| 650 | _aTechnical writing | ||
| 650 | _aHandbooks, manuals, etc | ||
| 700 | _aCorleissen, Zachary Sarah | ||
| 700 | _aLambourne, Jen | ||
| 700 | _aNunez, David | ||
| 700 | _aWaterhouse, Heidi | ||
| 942 |
_2ddc _cBK |
||