<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Troubleshooting on Eri Bastos</title>
    <link>https://ebastos.dev/categories/troubleshooting/</link>
    <description>Recent content in Troubleshooting on Eri Bastos</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 18 Feb 2023 13:17:51 +0000</lastBuildDate>
    <atom:link href="https://ebastos.dev/categories/troubleshooting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Troubleshooting with the OODA Loop</title>
      <link>https://ebastos.dev/2023/02/troubleshooting-with-the-ooda-loop/</link>
      <pubDate>Sat, 18 Feb 2023 13:17:51 +0000</pubDate>
      <guid>https://ebastos.dev/2023/02/troubleshooting-with-the-ooda-loop/</guid>
      <description>&lt;p&gt;The OODA Loop, a &lt;a href=&#34;https://amzn.to/3k6SKFA&#34;&gt;decision-making technique developed by the US Air Force for combat operations&lt;/a&gt;, is a helpful framework for troubleshooting. By following the four phases of the OODA Loop - Observe, Orient, Decide, Act - and repeating the process if necessary, you can break down complex problems into manageable steps and make informed decisions to find a solution.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://ebastos.dev/uploads/2023/02/image.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s how to apply the OODA Loop to troubleshooting:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Observe&lt;/strong&gt;: The first step is to observe the problem. Gather as much information as possible about the issue, including symptoms, errors, and messages. What else do you know about the problem? When did it start? What is the scope of the problem? What other pertinent information can you gather at this early stage? During this phase, it&amp;rsquo;s essential to focus on gathering quantity over quality. The more information you have in the beginning, the better. Leave to the decision phase on what to do with all this information.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
