<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Platform-Engineering on iqbalsyamil</title><link>https://iqbalsyamil.com/tags/platform-engineering/</link><description>Recent content in Platform-Engineering on iqbalsyamil</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://iqbalsyamil.com/tags/platform-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub wasn’t supposed to be the only way to ship</title><link>https://iqbalsyamil.com/posts/github-wasnt-supposed-to-be-the-only-way-to-ship/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://iqbalsyamil.com/posts/github-wasnt-supposed-to-be-the-only-way-to-ship/</guid><description>For more than five years, we built on top of GitHub. CI, automation, deployments, operational workflows — everything you can name. It was a good platform for that. We didn&amp;rsquo;t have to build another UI, invent another permission model, or teach everyone a different way to run things. Everything used the same language: GitHub Actions workflow YAML.
That consistency made onboarding easier. It also meant more and more of our ability to operate depended on one platform being available.</description></item></channel></rss>