Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Docs vs Tooling

Docs vs Tooling

External documentation is great in supporting developers using our code, but it’s not always enough and doesn't provide an immediate guidance to the developers using the code. Enter Tooling.

Tooling refers to the development tools/processes that make our code more maintainable and useable for others.

In this talk, I'd elaborate on docs, tooling, and how/why frontend developers can integrate both docs and tooling to enable other developers and themselves to effectively use their code.

Victor Ikechukwu

August 15, 2022
Tweet

More Decks by Victor Ikechukwu

Other Decks in Programming

Transcript

  1. Docs vs Tooling — How You can Support Developers to

    Effectively Use Your Code By Victor Ikechukwu
  2. I am Victor Ikechukwu. I code and write about code.

    2 Hell0! 👋 www.iamvictor.tech @Victor_codejs
  3. Table of contents ✗ What is Documentation? ✗ Why you

    need Documentation, and its benefits ✗ What is Tooling? ✗ Examples of Tooling and their benefits ✗ How you can combine both Documentation and Tooling to better support the developers that’ll use your code 3
  4. Documentation refers to all the materials that explains how our

    code works and how it should be used. 5
  5. Tooling refers to all development tools/processes that make our code

    more maintainable and useable for others. 13
  6. Key takeaway 35 As developers, managers, open-source maintainers we owe

    it to ourselves, to the community and to the developers who would use our code to incorporate documentation, best code practices and any other tools/process that will support them to use our code — That’s open source to me
  7. Thank YOU! You can find me at: @Victor_codejs 36 Link

    to slides — https://bit.ly/docs-vs-tooling