<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infrastructure on ROBOCO</title>
    <link>https://roboco.io/en/tags/infrastructure/</link>
    <description>Recent content in Infrastructure on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 26 Sep 2026 10:00:00 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Who Dared Cry Lock-In? - Infrastructure Dependence in the Vibe Coding Era</title>
      <link>https://roboco.io/en/posts/vibe-coding-infrastructure-lock-in/</link>
      <pubDate>Sat, 26 Sep 2026 10:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/vibe-coding-infrastructure-lock-in/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;“Who dared cry lock-in?”&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Plenty of people still prefer on-premises infrastructure in 2026. I understand the appeal of handling the machines and controlling every layer yourself. Latency, connections to existing equipment, and regulatory requirements can also make a self-managed environment necessary. But I find “we cannot use the cloud because it creates lock-in” hard to accept. &lt;strong&gt;Vibe coding has greatly reduced the cost of moving between clouds or back on-premises. The cost of remaining tied to facilities, equipment, and specialist operators has not gone away.&lt;/strong&gt; Which choice creates the deeper dependency?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
