<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Mostafa Khalil</title>
    <link>https://mostafakhalil.eu/post/</link>
    <description>Recent content in Posts on Mostafa Khalil</description>
    <image>
      <title>Mostafa Khalil</title>
      <url>https://mostafakhalil.eu/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://mostafakhalil.eu/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 27 May 2026 21:53:13 +0000</lastBuildDate>
    <atom:link href="https://mostafakhalil.eu/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Accidental Complexity</title>
      <link>https://mostafakhalil.eu/post/accidental-complexity/</link>
      <pubDate>Wed, 27 May 2026 21:53:13 +0000</pubDate>
      <guid>https://mostafakhalil.eu/post/accidental-complexity/</guid>
      <description>&lt;h3 id=&#34;a-quick-change&#34;&gt;A Quick Change&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;&amp;ldquo;This should be a quick change&amp;rdquo;&lt;/em&gt; - Said the engineer who ended up taking two weeks making the quick change.&lt;/p&gt;
&lt;p&gt;It is not uncommon for a seemingly benign change - one for which there is a general consensus that it is very easy; maybe too easy to even receive a concrete estimate - to end up taking longer than expected.&lt;/p&gt;
&lt;p&gt;A single delay can cascade in an entire workstream. Teams have been getting better at dealing with this type of delays though: engineers know how to raise their hand early, and short iterative sprints catch incomplete work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
