We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Continuous Documentation for your code

Formal Metadata

Title
Continuous Documentation for your code
Title of Series
Number of Parts
115
Author
Contributors
License
CC Attribution - NonCommercial - ShareAlike 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Do you document your code? Do you think it is important? Imagine that you need to get back to your code in 6 month after you wrote it, there is always a big possibility that you will have to spend some time to find out how this code works. Or if someone else wrote some code, which is already in production and your task is to fix a bug in it and there is no documentation and no one actually knows what this code does. There are more benefits of implementing continuous documentation for the code: easy to onboard new team members, easy to share knowledge, if this code is open source - easy to start contributing, easy to see purpose and motivation of each piece of code, easy to keep versioning for each new release of the code. In this talk you will see the difference between documentation types and a demo in the end of the talk.