{"product_id":"docs-for-developers-an-engineers-field-guide-to-technical-writing-paperback","title":"Docs for Developers: An Engineer's Field Guide to Technical Writing - Paperback","description":"\u003cdiv\u003e\u003cp style=\"text-align: right;\"\u003e\u003ca href=\"https:\/\/reportcopyrightinfringement.com\/\" target=\"_blank\" rel=\"nofollow\"\u003e\u003cb\u003eReport copyright infringement\u003c\/b\u003e\u003c\/a\u003e\u003c\/p\u003e\u003c\/div\u003e\u003cp\u003eby \u003cb\u003eJared Bhatti\u003c\/b\u003e (Author), \u003cb\u003eSarah Corleissen\u003c\/b\u003e (Author), \u003cb\u003eJen Lambourne\u003c\/b\u003e (Author)\u003c\/p\u003e\u003cp\u003e\u003c\/p\u003e\u003cp\u003eLearn 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.\u003c\/p\u003e\u003cp\u003eWell-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. \u003cbr\u003e\u003c\/p\u003e\u003cp\u003e\u003ci\u003eDocs for Developers\u003c\/i\u003e 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.\u003cbr\u003e\u003c\/p\u003e \u003cp\u003e\u003cb\u003eWhat You'll Learn\u003c\/b\u003e\u003cbr\u003e\u003c\/p\u003e\u003cp\u003e\u003cb\u003e\u003c\/b\u003e\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e Create friction logs and perform user research to understand your users' frustrations\u003c\/li\u003e\n\u003cli\u003eResearch, draft, and write different kinds of documentation, including READMEs, API documentation, tutorials, conceptual content, and release notes\u003c\/li\u003e\n\u003cli\u003ePublish and maintain documentation alongside regular code releases\u003c\/li\u003e\n\u003cli\u003eMeasure the success of the content you create through analytics and user feedback\u003c\/li\u003e\n\u003cli\u003eOrganize larger sets of documentation to help users find the right information at the right time\u003cp\u003e\u003c\/p\u003e\n\u003c\/li\u003e\n\u003c\/ul\u003e \u003cp\u003e\u003cb\u003eWho This Book Is For \u003c\/b\u003e\u003cbr\u003e\u003c\/p\u003e\u003cp\u003e\u003cb\u003e\u003c\/b\u003e\u003c\/p\u003e \u003cp\u003eIdeal 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.\u003cbr\u003e\u003c\/p\u003e \u003cp\u003e \u003c\/p\u003e\u003cbr\u003e\u003cp\u003e\u003c\/p\u003e\u003ch3\u003eBack Jacket\u003c\/h3\u003e\u003cp\u003e\u003c\/p\u003e\u003cp\u003eLearn 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.\u003c\/p\u003e\u003cp\u003eWell-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. \u003cbr\u003e\u003c\/p\u003e\u003cp\u003e\u003ci\u003eDocs for Developers\u003c\/i\u003e 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.\u003cbr\u003e\u003c\/p\u003e\u003cp\u003eYou will: \u003cbr\u003e\u003c\/p\u003e\u003cp\u003e\u003cb\u003e\u003c\/b\u003e\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003eCreate friction logs and perform user research to understand your users' frustrations\u003c\/li\u003e\n\u003cli\u003eResearch, draft, and write different kinds of documentation, including READMEs, API documentation, tutorials, conceptual content, and release notes\u003c\/li\u003e\n\u003cli\u003ePublish and maintain documentation alongside regular code releases\u003c\/li\u003e\n\u003cli\u003eMeasure the success of the content you create through analytics and user feedback\u003c\/li\u003e\n\u003cli\u003eOrganize larger sets of documentation to help users find the right information at the right time\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eAuthor Biography\u003c\/h3\u003e\u003cp\u003e\u003c\/p\u003e\u003cp\u003eJared Bhatti\u003cbr\u003e\u003c\/p\u003e\u003cbr\u003eJared is a Staff Technical Writer at Alphabet, and the co-founder of Google's Cloud documentation team. He's worked for the past 14 years documenting an array of projects at Alphabet, including Kubernetes, App Engine, Adsense, Google's data centers, and Google's environmental sustainability efforts. He currently leads technical documentation at Waymo and mentors several junior writers in the industry. \u003cp\u003e\u003c\/p\u003eZachary Sarah Corleissen \u003cp\u003e\u003c\/p\u003eZach began this book as the Lead Technical Writer for the Linux Foundation and ended it as Stripe's first Staff Technical Writer. Zach served as co-chair for Kubernetes documentation from 2017 until 2021, and has worked on developer docs previously at GitHub, Rackspace, and several startups. They enjoy speaking at conferences and love to mentor writers and speakers of all abilities and backgrounds. \u003cp\u003e\u003c\/p\u003eHeidi Waterhouse \u003cp\u003e\u003c\/p\u003eHeidi spent a couple decades at Microsoft, Dell Software, and many, many startups learning to communicate with and for developers. She currently works as a principal developer advocate at LaunchDarkly, but was reassured to find that technical communication is universal across all roles. \u003cp\u003e\u003c\/p\u003eDavid Nunez \u003cp\u003e\u003c\/p\u003eDavid heads up the technical writing organization at Stripe, where he founded the internal documentation team and wrote for Increment magazine. Before Stripe, he founded and led the technical writing organization at Uber and held a documentation leadership role at Salesforce. Having led teams that have written about cloud, homegrown infrastructure, self-driving trucks, and economic infrastructure, he's studied the many ways that technical documentation can shape the user experience. David also acts as an advisor for several startups in the knowledge platform space. \u003cp\u003e\u003c\/p\u003eJen Lambourne \u003cp\u003e\u003c\/p\u003eJen leads the technical writing and knowledge management discipline at Monzo Bank. Before her foray into fintech, she led a community of documentarians across the UK government as Head of Technical Writing at the Government Digital Service (GDS). Having moved from government to finance, she recognizes she's drawn to creating inclusive and user-centred content in traditionally unfriendly industries. She likes using developer tools to manage docs, demystifying the writing process for engineers, mentoring junior writers, and presenting her adventures in documentation at conferences.\u003cp\u003e\u003c\/p\u003e\u003cbr\u003e\n            \u003cdiv\u003e\n\u003cstrong\u003eNumber of Pages:\u003c\/strong\u003e 225\u003c\/div\u003e\n            \u003cdiv\u003e\n\u003cstrong\u003eDimensions:\u003c\/strong\u003e 0.53 x 9.21 x 6.14 IN\u003c\/div\u003e\n            \u003cdiv\u003e\n\u003cstrong\u003eIllustrated:\u003c\/strong\u003e Yes\u003c\/div\u003e\n            \u003cdiv\u003e\n\u003cstrong\u003ePublication Date:\u003c\/strong\u003e October 01, 2021\u003c\/div\u003e\n            ","brand":"BooksCloud","offers":[{"title":"Default Title","offer_id":44841192947814,"sku":"9781484272169","price":68.76,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0599\/7255\/0758\/files\/ZGxKWU9nMVVSbGd0bGhSbVdhZ29aZz09.webp?v=1772561119","url":"https:\/\/infinitylightwa.com\/products\/docs-for-developers-an-engineers-field-guide-to-technical-writing-paperback","provider":"Infinity Light","version":"1.0","type":"link"}