<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fuckup-Almanac on Shaharia Azam&#39;s Website | DevOps, Platform Engineering &amp; AI Insights</title>
    <link>https://shaharia.com/tags/fuckup-almanac/</link>
    <description>Recent content in Fuckup-Almanac on Shaharia Azam&#39;s Website | DevOps, Platform Engineering &amp; AI Insights</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 14 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://shaharia.com/tags/fuckup-almanac/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Beyond the Terminal: Why You Should Care About Systems Thinking</title>
      <link>https://shaharia.com/blog/beyond-the-terminal-why-you-should-care-about-systems-thinking/</link>
      <pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://shaharia.com/blog/beyond-the-terminal-why-you-should-care-about-systems-thinking/</guid>
      <description>Beyond the Terminal: Why You Should Care About Systems Thinking I usually write about specific engineering problems—how to optimize CI pipelines, how to manage AI context, or how to build tools that actually work. But today, I want to step back from the terminal for a moment.&#xA;Engineering is rarely just about code. It’s about understanding incentives, feedback loops, and how complex systems behave under pressure. A few months ago, a colleague of mine, Adam Korga—a pseudonym he’s quite open about on his site—introduced me to a way of thinking that bridges the gap between hard engineering and the &amp;ldquo;softer&amp;rdquo; sciences.</description>
    </item>
  </channel>
</rss>
