<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>iqbalsyamil</title><link>https://iqbalsyamil.com/</link><description>Recent content 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/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><item><title>about</title><link>https://iqbalsyamil.com/about/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://iqbalsyamil.com/about/</guid><description>&lt;p&gt;Hey, I&amp;rsquo;m Iqbal — SRE and platform engineer at &lt;strong&gt;Pintu&lt;/strong&gt;, a crypto exchange based in Indonesia.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve been at Pintu since the pre-seed days, all the way through Series B. I&amp;rsquo;ve seen the infrastructure go from a single VM, through Nomad, and eventually to Kubernetes — and I&amp;rsquo;ve had a hand in most of that journey.&lt;/p&gt;
&lt;p&gt;Along the way I&amp;rsquo;ve handled production infrastructure for some of Pintu&amp;rsquo;s core products — &lt;strong&gt;Pintu retail app&lt;/strong&gt;, &lt;strong&gt;Web3 Wallet&lt;/strong&gt;, and &lt;strong&gt;Rupiah Token&lt;/strong&gt; among them. Beyond the usual SRE work — monitoring, on-call, SLAs, keeping things up — I also own the CI platform end-to-end: the runner fleet, the tooling, the whole thing. It serves multiple monorepos and 100+ engineers across the company.&lt;/p&gt;</description></item><item><title>work with me</title><link>https://iqbalsyamil.com/work-with-me/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iqbalsyamil.com/work-with-me/</guid><description>&lt;p&gt;I help founders and early teams turn product ideas into reliable, production-ready systems — from zero to market.&lt;/p&gt;
&lt;p&gt;My work is useful when you know what you want to build, but need a technical path that can actually survive launch: architecture, infrastructure, delivery flow, reliability, observability, and the tradeoffs between moving fast and building something that will not collapse when people start using it.&lt;/p&gt;
&lt;p&gt;I have helped teams take products from early concept to functioning systems in production, with enough reliability and scalability to keep growing after launch.&lt;/p&gt;</description></item></channel></rss>