Pushing documentation (so it doesn't hurt anymore) by Markus Schlichting

Note: as the video registration was lost due to a technical issue, the recovered low quality audio has been remixed with the slides kindly provided by the speaker. We all love to put technology in place so it works, solves problems and eases somebodies live (or at least their job). But at some point the solutions created will be at risk to cause problems instead of solving them - and happy are those who find some useable documentation to the rescue! What makes good documentation? How much documentation is enough? How can we create useful documentation while we code? How can we integrate documentation into our dev-toolchains? Let's discuss these and more questions and find out how to put a checkmark to "docs" on out project's bucketlist with a smile 🙂