| 000 -LEADER |
|---|
| fixed length control field |
a |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
220106b xxu||||| |||| 00| 0 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
9781484272169 |
| 082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Classification number |
808.066 |
| Item number |
BHA |
| 100 ## - MAIN ENTRY--PERSONAL NAME |
|---|
| Personal name |
Bhatti, Jared |
| 245 ## - TITLE STATEMENT |
|---|
| Title |
Docs for developers : an engineer’s field guide to technical writing |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
|---|
| Name of publisher, distributor, etc |
Apress, |
| Date of publication, distribution, etc |
2021 |
| Place of publication, distribution, etc |
New York : |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
xxv, 225 p. ; |
| Other physical details |
ill., |
| Dimensions |
24 cm |
| 365 ## - TRADE PRICE |
|---|
| Price amount |
34.99 |
| Price type code |
EUR |
| Unit of pricing |
88.70 |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE |
|---|
| Bibliography, etc |
Includes bibliographical references and index. |
| 520 ## - SUMMARY, ETC. |
|---|
| Summary, etc |
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 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 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software documentation |
|
|---|
| Topical term or geographic name as entry element |
Technical writing |
|
|---|
| Topical term or geographic name as entry element |
Handbooks, manuals, etc |
| 700 ## - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
Corleissen, Zachary Sarah |
|
|---|
| Personal name |
Lambourne, Jen |
|
|---|
| Personal name |
Nunez, David |
|
|---|
| Personal name |
Waterhouse, Heidi |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) |
|---|
| Source of classification or shelving scheme |
|
| Item type |
Books |