In this episode we discus:
What is documentationBenefits of documentationDocumentation is critical for scaling, collaboration, and distributed teamsHow documentation benefits ourselvesLesli Lamport’s thoughts: To think, you have to write. If you’re thinkingwithout writing, you only think you’re thinking.
https://www.microsoft.com/en-us/research/wp-content/uploads/2016/07/leslie_lamport.pdfCode should not only be created for the compiler, but more importantly forother people
Importance of idioms, automatic code formatting, and code lintersDocumentation should live close to the code (embedded in the code, or Markdownin the same repository)
Benefits of MarkdownTrade-offs between Markdown and other formats like WordHow to optimize documentation for collaborationBiggest problem with documentation is that most of it gets stale and how toprevent this
Documentation can be a platform for thinking about a designDiscussion should happen around documentation, not the other way aroundUse CI tools to publish your documentationUseful tools: draw.io andTypora
The futility of emailing documentsStoring documents in Git and using pull requests (PRs) is a hugely beneficialfor collaboration
Cal Newport’s new book: A world without emailhttps://www.calnewport.com/books/a-world-without-email/Gitlab’s handbook has a lot of good ideashttps://about.gitlab.com/handbook/The more experienced you are, the more should you documentTools for generating documentation web sitesDocusaurusDocsy (Hugo)PandocmdBookmkdocsZolabook themeGitBookExample of collecting documentation from multiple projects and creating adocumentation site using Zola: https://github.com/simpleiot/docs.simpleiot.org
The TMPDIR handbook:https://gitlab.com/tmpdir/handbookJupyter Notebookhttps://jupyter.org/Treat documents as code, and code as documents!Available on your favorite podcast platform.
Discuss this episode at our