<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devops on Eri Bastos</title>
    <link>https://ebastos.dev/categories/devops/</link>
    <description>Recent content in Devops on Eri Bastos</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Oct 2023 14:35:02 +0000</lastBuildDate>
    <atom:link href="https://ebastos.dev/categories/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Continuous Improvement: The Path to Excellence</title>
      <link>https://ebastos.dev/2023/10/continuous-improvement-the-path-to-excellence/</link>
      <pubDate>Wed, 25 Oct 2023 14:35:02 +0000</pubDate>
      <guid>https://ebastos.dev/2023/10/continuous-improvement-the-path-to-excellence/</guid>
      <description>&lt;p&gt;The quest for operational excellence is unending in Cloud Engineering and Operations. We want to do more, better, faster, with fewer errors and with the same number of people. Amidst this quest, the philosophy of Continuous Improvement, &lt;a href=&#34;https://jamesclear.com/continuous-improvement&#34;&gt;a concept well-articulated by James Clear&lt;/a&gt;, finds a resounding echo. The essence of this philosophy lies in embracing a culture of making small, consistent improvements daily, which, over time, aggregate to substantial advancements.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-myths-holding-us-back&#34;&gt;The Myths Holding Us Back&lt;/h2&gt;&#xA;&lt;p&gt;Often, there&amp;rsquo;s a misconception in the operational realm that a massive overhaul of processes, done once and for all, will lead to a toil-free, highly automated environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Everything Sucks – Managing IT Risks: Strategies for IT Professionals.</title>
      <link>https://ebastos.dev/2023/04/everything-sucks-managing-it-risks-strategies-for-it-professionals/</link>
      <pubDate>Mon, 03 Apr 2023 01:00:00 +0000</pubDate>
      <guid>https://ebastos.dev/2023/04/everything-sucks-managing-it-risks-strategies-for-it-professionals/</guid>
      <description>&lt;p&gt;As someone who has worked in the IT industry for many years, I have realized that technology is far from perfect. In fact, I would go so far as to say that everything sucks when it comes to technology.&lt;/p&gt;&#xA;&lt;p&gt;IT professionals constantly deal with a never-ending barrage of issues, from unexpected hardware failures to software bugs and infrastructure breakdowns. It is Murphy&amp;rsquo;s Law all the way.&lt;/p&gt;&#xA;&lt;p&gt;And while we often joke about the shortcomings of operating systems like Windows, even the most reliable and robust systems like Linux are not immune to bugs and glitches. The sheer complexity of software development means that dozens of bugs are likely lurking in every thousand lines of code, making it impossible to catch them all.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Shift Left</title>
      <link>https://ebastos.dev/2023/02/shift-left/</link>
      <pubDate>Sat, 25 Feb 2023 14:19:04 +0000</pubDate>
      <guid>https://ebastos.dev/2023/02/shift-left/</guid>
      <description>&lt;p&gt;&lt;em&gt;Note: This article was originally written for my blog in Portuguese &lt;a href=&#34;https://geek.linuxman.pro.br/geek/shift-left&#34;&gt;back in 2021&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Shift Left is a practice in software development where the aim is to find defects as early in the process as possible. A &lt;a href=&#34;https://www.nist.gov/system/files/documents/director/planning/report02-3.pdf&#34;&gt;study from NIST&lt;/a&gt; shows that the cost of finding and fixing defects increases exponentially the farther it is found in the development cycle. Therefore, the ideal scenario is to find defects as early as possible, ideally in the design phase.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
