<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on Panji Gautama</title><link>https://panjigautama.com/categories/documentation/</link><description>Recent content in Documentation on Panji Gautama</description><generator>Hugo</generator><language>en</language><copyright>Copyright © Panji Gautama</copyright><lastBuildDate>Tue, 24 Jan 2023 21:19:09 +0000</lastBuildDate><atom:link href="https://panjigautama.com/categories/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Talking about Runbook</title><link>https://panjigautama.com/talking-about-runbook/</link><pubDate>Tue, 24 Jan 2023 21:18:29 +0000</pubDate><guid>https://panjigautama.com/talking-about-runbook/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/AchingIncompleteBetafish-size_restricted.gif" alt=""&gt;&lt;/p&gt;
&lt;h3 id="why-do-we-need-a-runbook"&gt;Why do we need a runbook?&lt;/h3&gt;
&lt;p&gt;the alert is only a signal, the very first step; reducing &lt;a href="https://www.splunk.com/en_us/data-insider/what-is-mean-time-to-repair.html"&gt;MTTR&lt;/a&gt; and solving the customer problem is the ultimate goal;&lt;/p&gt;
&lt;p&gt;an actionable alert is one of the repetitive tasks; Adding a runbook for the repetitive task will help to increase debugging, accuracy, and efficiency in the triaging process.&lt;/p&gt;
&lt;h3 id="but-what-exactly-is-runbook"&gt;But.. what exactly is runbook?&lt;/h3&gt;
&lt;p&gt;A &lt;strong&gt;runbook&lt;/strong&gt; is a series of steps and detailed instructions to solve common issues or tasks effectively.&lt;/p&gt;</description></item><item><title>Tech Debt Management</title><link>https://panjigautama.com/tech-debt-management/</link><pubDate>Tue, 08 Mar 2022 20:25:54 +0000</pubDate><guid>https://panjigautama.com/tech-debt-management/</guid><description>&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=n9BUA96ymC0"&gt;https://www.youtube.com/watch?v=n9BUA96ymC0&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;🔗 &lt;a href="https://www.slideshare.net/panjigautama/taming-technical-debt"&gt;https://www.slideshare.net/panjigautama/taming-technical-debt&lt;/a&gt;&lt;/p&gt;</description></item><item><title>On Establishing Technical Documentation at Mekari</title><link>https://panjigautama.com/on-establishing-technical-documentation-at-mekari/</link><pubDate>Thu, 04 Mar 2021 10:21:42 +0000</pubDate><guid>https://panjigautama.com/on-establishing-technical-documentation-at-mekari/</guid><description>&lt;p&gt;**&lt;br&gt;
**&lt;/p&gt;
&lt;p&gt;&lt;img src="https://panjigautama.com/images/tumblr_mcfqj603fq1rfjowdo1_500.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;We all hate time wasters. Documentation often is seen as one of these time wasters, mostly because it is boring to do. Planning is often seen as kind documentation, so there is a natural tendency to just skip this step for efficiency. However, people forget the hidden cost of skipping this documentation step: no agreement on shared understanding may cause the project will take a lot longer than people think, and this is only the beginning of other disadvantages of not having proper documentation.&lt;/p&gt;</description></item></channel></rss>