Dekorationsartikel gehören nicht zum Leistungsumfang.
Docs for Developers
An Engineer¿s Field Guide to Technical Writing
Taschenbuch von Jared Bhatti (u. a.)
Sprache: Englisch

63,75 €*

inkl. MwSt.

Versandkostenfrei per Post / DHL

Lieferzeit 1-2 Wochen

Kategorien:
Beschreibung
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.
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.
Über den Autor

Jared Bhatti

Jared 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.
Sarah Corleissen
Sarah (she/her, they/them) began this book as the Lead Technical Writer for the Linux Foundation and ended it as Stripe's first Staff Technical Writer. Sarah 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.
Heidi Waterhouse
Heidi 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.

David Nunez

David 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.
Jen Lambourne
Jen 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.
Zusammenfassung

Aligns the craft of writing with the craft of programming

Contains easy-to-follow processes, templates, and best practices for creating, organizing, and maintaining documentation

Written by experienced writers and developers from Google, The Linux Foundation, Stripe, LaunchDarkly, and Monzo,

Inhaltsverzeichnis
  1. Getting Started

  2. Researching documentation
    1. Understanding your users

    2. Cultivating empathy

    3. Understanding user desires, user needs, and company needs
    4. Recruiting users for research

  3. Research methods

    1. Reading code comments
    2. Trying it out

    3. Friction logs

    4. Running diverse and inclusive focus groups and interviews

    5. User journey mapping

  4. Identifying and working with stakeholders
    1. Finding your experts

    2. Collaborative documentation development

  5. Learning from existing content
    1. The value of design documents

    2. Finding examples in industry

  6. Designing documentation
    1. Defining your initial set of content

    2. Deciding your minimum viable documentation

    3. Drafting test and acceptance criteria
  7. Understanding content types

  8. Concepts, tutorials and reference documentation

  9. Code comments
  10. API specifications

  11. READMEs

  12. Guides

  13. Release notes

  14. Drafting documentation
    1. Setting yourself up for writing success

    2. Who is this for? Personas, requirements, content types

    3. Definition of done
    4. How to iterate

    Tools and tips for writing rough drafts

    1. Understanding your needs

    2. Choosing your writing tools (handwriting, text-only, productivity/measurement writing tools)

    3. "Hacks" to get started drafting content
  15. Mechanics

  16. Headings

  17. Paragraphs
  18. Lists

  19. Notes and warnings

  20. Conclusions/tests

  21. Using templates to form drafts

    1. Purpose of a template
    2. How to derive a template from existing docs

    3. How to take templates into text

  22. Gathering initial feedback

  23. Feedback methods

  24. Integrating feedback
  25. Getting feedback from difficult contributors

  26. Editing content for publication

    1. Determine destination

    2. Editing tools (Grammarly, linters, etc)

    3. Declaring good enough
  27. Recap, strategies, and reassurance

  28. Structuring sets of documentation

    1. Where content types live

    2. Concepts, tutorials and reference documentation

    3. Code comments
    4. API specifications

    5. READMEs

    6. Guides

    7. Release notes

  29. Designing your information architecture
    1. Content information architecture styles

    2. Designing for search

    3. Creating clear, well-lit paths through content
  30. User testing and maintenance

  31. Planning for document automation

  32. Integrating code samples and visual content
    1. Integrating code samples

    2. When and why to use code samples

    3. Creating concise, usable, maintainable samples
    4. Standardising your samples

  33. Using visual content: Screenshots, diagrams, and videos

    1. When your documentation may need visual content
    2. Making your visual content accessible

    3. Integrating screenshots, diagrams

    4. Videos
  34. Measuring documentation success

  35. How documentation succeeds

  36. Measuring different types of documentation quality
    1. Structural Quality

    2. Functional Quality

    3. Process Quality
  37. Measuring what you want to change

  38. Drawing conclusions from document metrics

  39. Working with contributors

  40. Defining how decisions are made

    1. Deciding on a governance structure
    2. Writing an effective Code of Conduct

  41. Choosing a content licence

    1. Code licenses
    2. Content licences

    Building and enforcing a style guide

  42. Editing submitted content and giving feedback

  43. Setting acceptability criteria

  44. Editing for accessibility and inclusion
  45. Editing for internationalization and translation

  46. Giving actionable feedback

  47. Planning and running a document sprint
  48. Maintaining documentation

  49. Creating a content review processes

    1. Assigning document owners
    2. Performing freshness checks on content

    Responding to documentation issues

    1. Separating documentation issues from product issues

    2. Responding to users

  50. Automating document maintenance
    1. Automating API and reference content

    2. Using doc linters

  51. Deleting and archiving content
  52. Wrapping up

Details
Erscheinungsjahr: 2021
Genre: Informatik
Rubrik: Naturwissenschaften & Technik
Medium: Taschenbuch
Seiten: 252
Inhalt: xxv
225 S.
31 s/w Illustr.
225 p. 31 illus.
ISBN-13: 9781484272169
ISBN-10: 1484272161
Sprache: Englisch
Ausstattung / Beilage: Paperback
Einband: Kartoniert / Broschiert
Autor: Bhatti, Jared
Corleissen, Sarah
Waterhouse, Heidi
Nunez, David
Lambourne, Jen
Auflage: 1st ed.
Besonderheit: Unsere Aufsteiger
Hersteller: Apress
Apress L.P.
Maße: 235 x 155 x 14 mm
Von/Mit: Jared Bhatti (u. a.)
Erscheinungsdatum: 01.10.2021
Gewicht: 0,388 kg
preigu-id: 120197028
Über den Autor

Jared Bhatti

Jared 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.
Sarah Corleissen
Sarah (she/her, they/them) began this book as the Lead Technical Writer for the Linux Foundation and ended it as Stripe's first Staff Technical Writer. Sarah 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.
Heidi Waterhouse
Heidi 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.

David Nunez

David 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.
Jen Lambourne
Jen 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.
Zusammenfassung

Aligns the craft of writing with the craft of programming

Contains easy-to-follow processes, templates, and best practices for creating, organizing, and maintaining documentation

Written by experienced writers and developers from Google, The Linux Foundation, Stripe, LaunchDarkly, and Monzo,

Inhaltsverzeichnis
  1. Getting Started

  2. Researching documentation
    1. Understanding your users

    2. Cultivating empathy

    3. Understanding user desires, user needs, and company needs
    4. Recruiting users for research

  3. Research methods

    1. Reading code comments
    2. Trying it out

    3. Friction logs

    4. Running diverse and inclusive focus groups and interviews

    5. User journey mapping

  4. Identifying and working with stakeholders
    1. Finding your experts

    2. Collaborative documentation development

  5. Learning from existing content
    1. The value of design documents

    2. Finding examples in industry

  6. Designing documentation
    1. Defining your initial set of content

    2. Deciding your minimum viable documentation

    3. Drafting test and acceptance criteria
  7. Understanding content types

  8. Concepts, tutorials and reference documentation

  9. Code comments
  10. API specifications

  11. READMEs

  12. Guides

  13. Release notes

  14. Drafting documentation
    1. Setting yourself up for writing success

    2. Who is this for? Personas, requirements, content types

    3. Definition of done
    4. How to iterate

    Tools and tips for writing rough drafts

    1. Understanding your needs

    2. Choosing your writing tools (handwriting, text-only, productivity/measurement writing tools)

    3. "Hacks" to get started drafting content
  15. Mechanics

  16. Headings

  17. Paragraphs
  18. Lists

  19. Notes and warnings

  20. Conclusions/tests

  21. Using templates to form drafts

    1. Purpose of a template
    2. How to derive a template from existing docs

    3. How to take templates into text

  22. Gathering initial feedback

  23. Feedback methods

  24. Integrating feedback
  25. Getting feedback from difficult contributors

  26. Editing content for publication

    1. Determine destination

    2. Editing tools (Grammarly, linters, etc)

    3. Declaring good enough
  27. Recap, strategies, and reassurance

  28. Structuring sets of documentation

    1. Where content types live

    2. Concepts, tutorials and reference documentation

    3. Code comments
    4. API specifications

    5. READMEs

    6. Guides

    7. Release notes

  29. Designing your information architecture
    1. Content information architecture styles

    2. Designing for search

    3. Creating clear, well-lit paths through content
  30. User testing and maintenance

  31. Planning for document automation

  32. Integrating code samples and visual content
    1. Integrating code samples

    2. When and why to use code samples

    3. Creating concise, usable, maintainable samples
    4. Standardising your samples

  33. Using visual content: Screenshots, diagrams, and videos

    1. When your documentation may need visual content
    2. Making your visual content accessible

    3. Integrating screenshots, diagrams

    4. Videos
  34. Measuring documentation success

  35. How documentation succeeds

  36. Measuring different types of documentation quality
    1. Structural Quality

    2. Functional Quality

    3. Process Quality
  37. Measuring what you want to change

  38. Drawing conclusions from document metrics

  39. Working with contributors

  40. Defining how decisions are made

    1. Deciding on a governance structure
    2. Writing an effective Code of Conduct

  41. Choosing a content licence

    1. Code licenses
    2. Content licences

    Building and enforcing a style guide

  42. Editing submitted content and giving feedback

  43. Setting acceptability criteria

  44. Editing for accessibility and inclusion
  45. Editing for internationalization and translation

  46. Giving actionable feedback

  47. Planning and running a document sprint
  48. Maintaining documentation

  49. Creating a content review processes

    1. Assigning document owners
    2. Performing freshness checks on content

    Responding to documentation issues

    1. Separating documentation issues from product issues

    2. Responding to users

  50. Automating document maintenance
    1. Automating API and reference content

    2. Using doc linters

  51. Deleting and archiving content
  52. Wrapping up

Details
Erscheinungsjahr: 2021
Genre: Informatik
Rubrik: Naturwissenschaften & Technik
Medium: Taschenbuch
Seiten: 252
Inhalt: xxv
225 S.
31 s/w Illustr.
225 p. 31 illus.
ISBN-13: 9781484272169
ISBN-10: 1484272161
Sprache: Englisch
Ausstattung / Beilage: Paperback
Einband: Kartoniert / Broschiert
Autor: Bhatti, Jared
Corleissen, Sarah
Waterhouse, Heidi
Nunez, David
Lambourne, Jen
Auflage: 1st ed.
Besonderheit: Unsere Aufsteiger
Hersteller: Apress
Apress L.P.
Maße: 235 x 155 x 14 mm
Von/Mit: Jared Bhatti (u. a.)
Erscheinungsdatum: 01.10.2021
Gewicht: 0,388 kg
preigu-id: 120197028
Warnhinweis

Ähnliche Produkte

Ähnliche Produkte