<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aws on ROBOCO</title>
    <link>https://roboco.io/en/tags/aws/</link>
    <description>Recent content in Aws on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 29 Mar 2026 16:00:00 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Serverless Autoresearch: A Record of Making an ML Experiment Pipeline Serverless Through Vibe Coding</title>
      <link>https://roboco.io/en/posts/serverless-autoresearch-vibe-coding/</link>
      <pubDate>Sun, 29 Mar 2026 16:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/serverless-autoresearch-vibe-coding/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;The real value of vibe coding is not only in writing code fast. It is in designing a way of operating that lets you repeat expensive experiments more cheaply and more quickly.&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;Most people first associate vibe coding with web app prototyping or CRUD automation. But ROBOCO&amp;rsquo;s &lt;a href=&#34;https://github.com/roboco-io/serverless-autoresearch&#34;&gt;&lt;code&gt;serverless-autoresearch&lt;/code&gt;&lt;/a&gt; repository widens that frame considerably. Instead of the &amp;ldquo;tie up a single H100 for several hours&amp;rdquo; approach that Andrej Karpathy&amp;rsquo;s &lt;code&gt;autoresearch&lt;/code&gt; presupposes, this project builds a structure that runs parallel experiments in short, explosive bursts on AWS SageMaker Spot.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&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>
  </channel>
</rss>
