<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Essay on iqbalsyamil</title><link>https://iqbalsyamil.com/tags/essay/</link><description>Recent content in Essay on iqbalsyamil</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://iqbalsyamil.com/tags/essay/index.xml" rel="self" type="application/rss+xml"/><item><title>The floor, not the ceiling</title><link>https://iqbalsyamil.com/posts/the-floor-not-the-ceiling/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://iqbalsyamil.com/posts/the-floor-not-the-ceiling/</guid><description>&lt;p&gt;&lt;em&gt;Three attempts. Three different ways in. One lesson about how work actually gets done.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-first-attempt"&gt;The first attempt&lt;/h2&gt;
&lt;p&gt;A few years ago I became obsessed with a problem nobody had officially asked me to solve: we had no reliable way to know who owned what service. Ownership was scattered — in people&amp;rsquo;s heads, in Slack threads, in documentation that was already outdated the moment it was written.&lt;/p&gt;
&lt;p&gt;So I started collecting it. Built a Notion database, mapped services to teams, planned to migrate it into our own system eventually. The vision was clear to me: you can&amp;rsquo;t build an internal developer platform without knowing what you&amp;rsquo;re building it on top of.&lt;/p&gt;</description></item><item><title>Good ideas don't ship on merit</title><link>https://iqbalsyamil.com/posts/good-ideas-dont-ship-on-merit/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://iqbalsyamil.com/posts/good-ideas-dont-ship-on-merit/</guid><description>&lt;p&gt;&lt;em&gt;Four years of CI, two market cycles, and the thing we still haven&amp;rsquo;t solved&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;The pattern&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;There&amp;rsquo;s a conversation that happens in every cycle. Different quarter, different context, same shape. Something is expensive or broken or inefficient. Everyone senses it. The urgency peaks, then dissolves. The moment passes and we move on. Next cycle, the conversation returns — same contours, different numbers.&lt;/p&gt;
&lt;p&gt;After enough cycles you stop being surprised by the pattern and start asking a different question: what would it look like to get ahead of it instead of reacting to it?&lt;/p&gt;</description></item></channel></rss>