<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Best Practices on Miro&#39;s World</title>
    <link>https://miroadamy.com/categories/best-practices/</link>
    <description>Recent content in Best Practices on Miro&#39;s World</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Miro Adamy</copyright>
    <lastBuildDate>Mon, 23 Nov 2020 13:00:00 +0800</lastBuildDate><atom:link href="https://miroadamy.com/categories/best-practices/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Documenting multi-repository projects</title>
      <link>https://miroadamy.com/posts/2020-11-23-documentation-multi-repo/</link>
      <pubDate>Mon, 23 Nov 2020 13:00:00 +0800</pubDate>
      
      <guid>https://miroadamy.com/posts/2020-11-23-documentation-multi-repo/</guid>
      <description>&lt;p&gt;This blog post is a de-powerpointized version of a brownbag session in Pivotree. The goal&#xA;was to increase awareness of tools and techniques for information / knowledge capture in the projects, specifically focusing on producing quality documentation so that everybody in project can access it and contribute to it,&#xA;not only developers. We wanted to look at the tools that would allow engineers keep using their tools of trade&#xA;(without impact on developer’s productivity) and at the same time make the information available without&#xA;duplication of work to increase re-findability of information.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
