<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Not-DevOps</title>
    <link>//localhost:1313/</link>
    <description>Recent content on Not-DevOps</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="//localhost:1313/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Breaking: Sysadmin Achieves “Permanent Stability” by Scheduling Cronjobs on February 30th</title>
      <link>//localhost:1313/posts/cronjob-party/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/cronjob-party/</guid>
      <description>&lt;p&gt;In what insiders are calling &lt;em&gt;“long-term thinking taken just a bit too far”&lt;/em&gt;, engineers worldwide have confirmed that scheduling cron jobs on &lt;strong&gt;February 30th&lt;/strong&gt; is not a bug—it’s a feature.&lt;/p&gt;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&lt;blockquote class=&#34;blockquote-regular&#34;&gt;&#xA;  &lt;p&gt;“It’s a clean, intentional disable,” explained one senior SRE.&lt;br&gt;&#xA;“No comments, no flags, no documentation needed. You just pick a date that doesn’t exist. Future-proof.”&lt;/p&gt;&#xA;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;For years, this technique has been quietly deployed in production systems:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Legacy cleanup scripts → &lt;strong&gt;February 30th&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;Dangerous database migrations → &lt;strong&gt;February 30th&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;That one job nobody understands → &lt;strong&gt;especially February 30th&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&lt;blockquote class=&#34;blockquote-regular&#34;&gt;&#xA;  &lt;p&gt;“It’s perfect,” another engineer added.&lt;br&gt;&#xA;“You don’t delete the job—you just move it… outside of reality.”&lt;/p&gt;</description>
    </item>
    <item>
      <title>Chaos Engineering gone too far: Namespace deletion roulette</title>
      <link>//localhost:1313/posts/kubernetes-roulette/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/kubernetes-roulette/</guid>
      <description>&lt;p&gt;Once upon a time, chaos engineering meant carefully injecting faults to test resilience. Thoughtful experiments. Controlled blast radius. Maybe unplugging a node while everyone watched nervously.&lt;/p&gt;&#xA;&lt;p&gt;That time is over.&lt;/p&gt;&#xA;&lt;p&gt;Welcome to &lt;strong&gt;Full-Send Chaos Engineering™&lt;/strong&gt;, where the goal is no longer to &lt;em&gt;learn&lt;/em&gt;, but to &lt;strong&gt;feel something again&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;1-namespace-deletion-roulette-&#34;&gt;1. Namespace Deletion Roulette 🎯&lt;/h2&gt;&#xA;&lt;p&gt;Why waste time designing experiments when you can let fate decide? Namespace Deletion Roulette brings excitement back to your otherwise predictable production outages.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How Smart Businesses Make Money from App Delays: The Sleep() Trick Behind Success</title>
      <link>//localhost:1313/posts/strategic-latency-monetization/</link>
      <pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/strategic-latency-monetization/</guid>
      <description>&lt;p&gt;In today’s competitive tech landscape, innovation is no longer about solving problems—it’s about &lt;em&gt;creating just enough of them to monetize the solution&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Enter the revolutionary methodology: &lt;strong&gt;Delay-Driven Revenue Optimization (DDRO™)&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The idea is simple: build a beautiful, scalable app… then quietly sprinkle in a few &lt;code&gt;sleep()&lt;/code&gt; calls.&lt;/p&gt;&#xA;&lt;p&gt;Not enough to break things. Just enough to make users sigh.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;phase-1-the-subtle-stall&#34;&gt;Phase 1: The Subtle Stall&lt;/h3&gt;&#xA;&lt;p&gt;At launch, everything works perfectly—within acceptable latency of the human soul.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Art of Sabotaging Daily Stand-Ups: A Masterclass in DevOps Dysfunction</title>
      <link>//localhost:1313/posts/the-art-of-sabotaging-daily-stand-ups/</link>
      <pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/the-art-of-sabotaging-daily-stand-ups/</guid>
      <description>&lt;p&gt;In the thrilling world of DevOps, there exists a sacred ritual known as the &lt;strong&gt;daily stand-up meeting&lt;/strong&gt;. While most teams strive for efficiency and collaboration, there are those rare few who have perfected the art of turning this simple gathering into a &lt;strong&gt;Kafkaesque nightmare&lt;/strong&gt;. Strap in, because we&amp;rsquo;re about to embark on a journey through the worst way to conduct daily stand-ups!&lt;/p&gt;&#xA;&lt;h3 id=&#34;scheduling-shenanigans&#34;&gt;Scheduling Shenanigans&lt;/h3&gt;&#xA;&lt;p&gt;First things first, let&amp;rsquo;s ensure nobody actually has time for this meeting. Schedule the stand-up at 4:45 PM, just before everyone&amp;rsquo;s desperate dash to leave the office. Throw in a dash of unpredictability by changing the meeting time every day, so your team can never really plan anything outside of work. After all, who needs a life outside the office?&lt;/p&gt;</description>
    </item>
    <item>
      <title>DevOps Revolution: Converting Security Budget into a &#39;Hack Tax&#39; Budget</title>
      <link>//localhost:1313/posts/devops-revolution-convert-security-budget-to-hack-tax/</link>
      <pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/devops-revolution-convert-security-budget-to-hack-tax/</guid>
      <description>&lt;p&gt;In a &lt;strong&gt;bold&lt;/strong&gt; and &lt;strong&gt;innovative&lt;/strong&gt; move, our company has embarked on a DevOps transformation that has left many scratching their heads and others reaching for their wallets. We&amp;rsquo;ve proudly transitioned our &lt;strong&gt;security budget&lt;/strong&gt; into a cutting-edge &lt;strong&gt;&amp;ldquo;Hack Tax&amp;rdquo;&lt;/strong&gt; fund, and the results are nothing short of &lt;strong&gt;astounding&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-concept-paying-hackers-instead-of-prevention&#34;&gt;The Concept: Paying Hackers Instead of Prevention&lt;/h2&gt;&#xA;&lt;p&gt;The concept is &lt;strong&gt;simple&lt;/strong&gt;, really: why bother investing in those pesky security measures when we can just put that money aside to &lt;strong&gt;pay off hackers&lt;/strong&gt; if and when they strike? After all, &lt;strong&gt;prevention&lt;/strong&gt; is so last season. In the ever-evolving world of &lt;strong&gt;technology&lt;/strong&gt;, why not embrace the &lt;strong&gt;chaos&lt;/strong&gt; and &lt;strong&gt;unpredictability&lt;/strong&gt; that comes with being perpetually vulnerable?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mastering the Art of Writing Horrendous Post-Mortems: A DevOps Guide</title>
      <link>//localhost:1313/posts/mastering-the-art-of-writing-horrendous-post-mortems/</link>
      <pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/mastering-the-art-of-writing-horrendous-post-mortems/</guid>
      <description>&lt;p&gt;Ah, post-mortems, the time-honored tradition of &lt;strong&gt;blaming&lt;/strong&gt;, &lt;strong&gt;finger-pointing&lt;/strong&gt;, and conveniently ignoring your own mistakes. Why settle for constructive, productive post-mortems when you can excel at writing &lt;strong&gt;abysmal&lt;/strong&gt; ones? Join us on this satirical journey as we explore the world of &lt;strong&gt;poorly written post-mortems&lt;/strong&gt;, where chaos reigns supreme, and accountability is but a distant dream.&lt;/p&gt;&#xA;&lt;h2 id=&#34;skip-the-introduction&#34;&gt;Skip the Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Who needs context anyway? Jump right into the &lt;strong&gt;technical details&lt;/strong&gt; without bothering to explain what went wrong or why it matters. Your readers will surely appreciate the &lt;strong&gt;enigma&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Catastrophic DevOps: How to NOT Manage On-Call</title>
      <link>//localhost:1313/posts/catastrophic-devops-how-to-not-manage-on-call/</link>
      <pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/catastrophic-devops-how-to-not-manage-on-call/</guid>
      <description>&lt;p&gt;Ah, on-call duty, the crown jewel of modern DevOps. It&amp;rsquo;s like a never-ending adventure, where your pagers are your trusty sidekicks, and your sleep schedule? Well, who needs sleep anyway? In this guide, we&amp;rsquo;re going to explore the absolute worst ways to manage on-call, ensuring that your team&amp;rsquo;s misery knows no bounds. After all, who needs stability, sanity, or a good night&amp;rsquo;s sleep when you can embrace chaos and frustration?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Revolutionize Your DevOps Job Search with Our Disruptive Cover Letter Strategy!</title>
      <link>//localhost:1313/posts/revolutionize-devops-job-search/</link>
      <pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/revolutionize-devops-job-search/</guid>
      <description>&lt;p&gt;Tired of sending out cover letters and not receiving responses?&lt;/p&gt;&#xA;&lt;p&gt;Fed up with the traditional recruitment game that leaves you feeling bored and overlooked?&lt;/p&gt;&#xA;&lt;p&gt;Look no further! We&amp;rsquo;re here to introduce a fresh and disruptive approach to help you stand out in the competitive DevOps job market.&lt;/p&gt;&#xA;&lt;h2 id=&#34;cover-letter&#34;&gt;Cover Letter&lt;/h2&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;&lt;em&gt;Dear Recruiter,&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;I want to express my deep lack of interest in the position of DevOps engineer within your company. After carefully reviewing the job description, I am convinced that my technical skills and experience &lt;strong&gt;do not align&lt;/strong&gt; with what you are looking for at all.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Agile Poker Planning: Where Random Estimations Lead to Random Outcomes</title>
      <link>//localhost:1313/posts/agile-random-poker-planning/</link>
      <pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/posts/agile-random-poker-planning/</guid>
      <description>&lt;p&gt;In the fast-paced realm of software development, the agile methodology stands tall, promising adaptability, flexibility, and closer collaboration between development teams and stakeholders. At the heart of agile planning lies the widely adopted &lt;a href=&#34;https://en.wikipedia.org/wiki/Planning_poker&#34;&gt;&amp;ldquo;Agile Poker Planning&amp;rdquo;&lt;/a&gt; technique. But hold on to your hats because we&amp;rsquo;ve just unleashed a game-changing twist that&amp;rsquo;s poised to disrupt the way you approach software estimation. Introducing the &amp;ldquo;Random Estimation&amp;rdquo; edition of Agile Poker Planning!&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-thrill-of-the-draw&#34;&gt;The Thrill of the Draw&lt;/h2&gt;&#xA;&lt;p&gt;Imagine this scenario: your agile development team assembles in a conference room, armed with &lt;strong&gt;decks of cards&lt;/strong&gt; featuring numbers corresponding to story points. The objective? Estimate the &lt;strong&gt;complexity and effort&lt;/strong&gt; required for each task. But predictable estimation methods are so yesterday. Instead, why not put your project&amp;rsquo;s destiny in the hands of chance?&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>//localhost:1313/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>//localhost:1313/about/</guid>
      <description>&lt;h1 id=&#34;about&#34;&gt;About&lt;/h1&gt;&#xA;&lt;p&gt;Because sometimes DevOps deserves satire more than stress.&lt;/p&gt;&#xA;&lt;p&gt;Some articles (well, all) may have been written with the assistance of &lt;a href=&#34;https://en.wikipedia.org/wiki/Large_language_model&#34;&gt;large language models (LLMs)&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Your YAML isn’t perfect, but you are ❤️. Follow us on &lt;a href=&#34;https://x.com/not_devops&#34;&gt;Twitter&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
