<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Murphy&#39;s Law on DevopsTrain</title>
    <link>https://devopstrain.lifeisfile.com/tags/murphys-law/</link>
    <description>Recent content in Murphy&#39;s Law on DevopsTrain</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>©, Alex Babochkin</copyright>
    <lastBuildDate>Fri, 04 Oct 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstrain.lifeisfile.com/tags/murphys-law/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Murphy&#39;s law</title>
      <link>https://devopstrain.lifeisfile.com/post/murphys-law/</link>
      <pubDate>Fri, 04 Oct 2024 00:00:00 +0000</pubDate>
      
      <guid>https://devopstrain.lifeisfile.com/post/murphys-law/</guid>
      <description>
        
          
            How Murphy&#39;s law works in devops
Let me tell you how I spent the last week of August and the beginning of September...
It just so happened that out of our entire devops team I was left on my own — you know how it is, vacation season and all that. Fine, not the first time, nothing unusual. But I ended up looking after a project that had been built before my time, and, to put it mildly, not always on the best devops practices 👽
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
