<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI-Adoption on ROBOCO</title>
    <link>https://roboco.io/en/tags/ai-adoption/</link>
    <description>Recent content in AI-Adoption on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 26 Mar 2026 17:26:21 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/ai-adoption/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Line Between Repository Rules and Personal Taste in the Vibe Coding Era</title>
      <link>https://roboco.io/en/posts/vibe-coding-rules-vs-taste/</link>
      <pubDate>Thu, 26 Mar 2026 17:26:21 +0900</pubDate>
      <guid>https://roboco.io/en/posts/vibe-coding-rules-vs-taste/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;The job of AGENTS.md is not to clone your developers. It is to pin down only the boundaries where accidents must be prevented.&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;p&gt;Teams that adopt vibe coding soon run into a similar question. Once you start putting an &lt;code&gt;AGENTS.md&lt;/code&gt; or &lt;code&gt;CLAUDE.md&lt;/code&gt; in every repository to tell AI agents the rules, it becomes murky how far you should pin things down as shared rules and where you should leave things to individual taste. Draw that line wrong and two problems appear at once: the safety rules that absolutely must hold get loose, while choices that are really just preferences become needlessly rigid.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Organizational Design for Adopting Vibe Coding</title>
      <link>https://roboco.io/en/posts/organizational-design-for-vibe-coding/</link>
      <pubDate>Fri, 20 Mar 2026 21:23:40 +0900</pubDate>
      <guid>https://roboco.io/en/posts/organizational-design-for-vibe-coding/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;Whether vibe coding succeeds or fails comes down to organizational design: whether the team can verify and ship AI-generated changes in a repeatable, safe way.&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;p&gt;Many organizations understand vibe coding as little more than &amp;ldquo;a way for developers to produce code faster.&amp;rdquo; So the adoption conversation usually starts with tooling. But what actually decides success or failure in the field is organizational structure, not the tool or the model&amp;rsquo;s performance.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Guide to Enterprise AI Adoption</title>
      <link>https://roboco.io/en/posts/ai-adoption-guide/</link>
      <pubDate>Fri, 26 Dec 2025 09:16:27 +0900</pubDate>
      <guid>https://roboco.io/en/posts/ai-adoption-guide/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;The essence of AI adoption is not bolting on a new tool. It is changing the very way an organization creates customer value, faster and more accurately.&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;Meetings about adopting AI tend to start from the same question. &amp;ldquo;Our competitors are already using it, so when should we start?&amp;rdquo; Tool comparisons, license budgets, and training schedules follow soon after. That much is easy. The genuinely hard part comes next. It&amp;rsquo;s common for the way people work not to change fundamentally even after months, or for only a fraction of the organization to use it before it fizzles out. At some point AI stops being an &amp;ldquo;innovation project&amp;rdquo; and becomes &amp;ldquo;one more subscription fee.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
