<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tips on ROBOCO</title>
    <link>https://roboco.io/en/tags/tips/</link>
    <description>Recent content in Tips on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Jun 2025 13:38:18 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/tips/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agentic Coding Recommendations, Explained</title>
      <link>https://roboco.io/en/posts/agentic-coding-recommendations-explained/</link>
      <pubDate>Tue, 17 Jun 2025 13:38:18 +0900</pubDate>
      <guid>https://roboco.io/en/posts/agentic-coding-recommendations-explained/</guid>
      <description>&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;blockquote&gt;&#xA;&lt;p&gt;This post is based on Armin Ronacher&amp;rsquo;s blog article &lt;a href=&#34;https://lucumr.pocoo.org/2025/6/12/agentic-coding/&#34;&gt;&amp;ldquo;Agentic Coding Recommendations&amp;rdquo;&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;h2 id=&#34;foreword&#34;&gt;Foreword&lt;/h2&gt;&#xA;&lt;p&gt;A few days ago I came across Armin Ronacher&amp;rsquo;s blog post &lt;a href=&#34;https://lucumr.pocoo.org/2025/6/12/agentic-coding/&#34;&gt;&amp;ldquo;Agentic Coding Recommendations&amp;rdquo;&lt;/a&gt; on the developer community &lt;a href=&#34;https://news.hada.io/topic?id=21435&#34;&gt;Geek News&lt;/a&gt;, and it left quite an impression on me. Armin is best known as the creator of the Flask web framework, and his insights on vibe coding line up closely with the direction Roboco is heading. In this post I want to unpack the core ideas in Armin&amp;rsquo;s article in an accessible way, for people just getting started with vibe coding through tools like Claude Code, Cursor, and Windsurf.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Drawing Architecture Diagrams with AI</title>
      <link>https://roboco.io/en/posts/how-to-draw-diagram/</link>
      <pubDate>Sat, 14 Jun 2025 12:35:06 +0900</pubDate>
      <guid>https://roboco.io/en/posts/how-to-draw-diagram/</guid>
      <description>&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;When people do vibe coding, they often assume the code alone is enough. Reality says otherwise. Code without documentation is like setting off on a trip without a map. If nobody knows where the destination is or what the route looks like, nobody will come along. Documentation matters especially in vibe coding because code isn&amp;rsquo;t merely there to run — it exists to convey your ideas and design intent accurately to other people. Documentation smooths collaboration, clarifies where a project is headed, and ultimately forms the foundation of a sustainable development environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Does English Work Better Than Korean for Vibe Coding?</title>
      <link>https://roboco.io/en/posts/vibecoding-lang-choice/</link>
      <pubDate>Fri, 04 Apr 2025 08:12:04 +0900</pubDate>
      <guid>https://roboco.io/en/posts/vibecoding-lang-choice/</guid>
      <description>&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;There is one question people commonly wonder about when it comes to vibe coding, that is, developing with a large language model (LLM) like GPT: &amp;ldquo;Is there a difference in the quality of the work when I talk to the model in Korean versus English?&amp;rdquo; To give the conclusion first, in my experience and by the way LLMs work, the language itself does not change the quality of the work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
