<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daiki Teramoto on Medium]]></title>
        <description><![CDATA[Stories by Daiki Teramoto on Medium]]></description>
        <link>https://medium.com/@daikiteramoto?source=rss-6d6d856f5b28------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zoT95BGmbLgAODrG.</url>
            <title>Stories by Daiki Teramoto on Medium</title>
            <link>https://medium.com/@daikiteramoto?source=rss-6d6d856f5b28------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:07:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daikiteramoto/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Devin Logbook — Day 1]]></title>
            <link>https://medium.com/@daikiteramoto/devin-logbook-day-1-d5de3aff01d6?source=rss-6d6d856f5b28------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5de3aff01d6</guid>
            <category><![CDATA[devin]]></category>
            <dc:creator><![CDATA[Daiki Teramoto]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 02:43:11 GMT</pubDate>
            <atom:updated>2025-01-12T02:43:11.792Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Devin Logbook — Day 1</strong></h3><blockquote>This article is a translated version of my Japanese blog post, originally published <a href="https://editor.note.com/notes/nd2f47ab20c26">here</a>.</blockquote><p>I finally purchased Devin for $500.<br> Today, I’ll share my experience from onboarding to completing my first task.</p><h3>A Unique Purchase Experience</h3><p>When signing up for Devin, a chat-like interface appears, asking for your name and organization. Then, a button labeled <strong>“Purchase Subscription”</strong> pops up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*paPsbYPeTISvtjhoTyEZ9w.jpeg" /></figure><p>The phrasing <strong>“To work with me”</strong> felt quite unique, as if emphasizing a sense of personification and world-building.</p><p>By the way, the payment was processed through Stripe.</p><h3>Onboarding</h3><p>After signing up, the next step is linking your accounts:</p><ul><li><strong>GitHub:</strong> Required, supports both personal and organizational accounts.</li><li><strong>Slack:</strong> Optional but useful for notifications.</li><li><strong>Slack Connect:</strong> Optional, for contacting Cognitive’s support team.</li></ul><p>For those curious about the permissions, here are some screenshots of the installation process for both GitHub and Slack.</p><ul><li><a href="https://gyazo.com/ae456637c76bc2c0d025b34ec4288502">Gyazo</a></li><li><a href="https://gyazo.com/ea760159af7fce31a7e5749b5729c158">Gyazo</a></li></ul><p>Next, you configure the repositories where Devin will work. Devin can access any authorized repositories, but its work environment resets after each session.</p><p>To avoid the inefficiency of redoing a full git clone every time, you can save a <strong>snapshot</strong> of frequently used environments. Think of it like <strong>GitHub Workspaces</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lJ6Iy5vcsxBalenfNIo_4g.png" /></figure><p>Devin’s work environment runs <strong>VSCode Remote</strong>, where you can manually run commands like npm install when needed. At this stage, Devin is still not &quot;on duty&quot; yet, so you handle the setup yourself.<br> <em>(Side note: This feels a bit like pre-deployment setup before handing a PC to a new employee.)</em></p><h3>Prompt Customization</h3><p>The final onboarding step is setting up the prompts. Impressively, the default prompt already aligns quite well with the repository’s context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1iVzdjhinGmar67A9MwelA.png" /></figure><p>For example, it recognizes that the project is in <strong>Node.js</strong>, identifies what the CI checks for, and even includes tips like:<br> <em>“Local tests might not run properly, so don’t worry too much.”</em> (That last part felt a bit unnecessary, though.)</p><p>Though the default was sufficient, my inner engineer kicked in, and I ended up tweaking the prompt a bit.</p><p>With that, onboarding was complete!</p><h3>🎉 Devin’s First Day on the Job</h3><p>Now it was time to assign Devin its first task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xR6UMmpmdiOaNByf6dTK_Q.png" /></figure><p>I started with a simple test run using the preset:</p><ul><li>Access the configured repository</li><li>Run lint</li><li>Make a minor change and create a pull request</li></ul><p>Even in this basic task, the inclusion of run lint showed the prompt was being followed closely (though running lint before changes felt a bit off).</p><p>Upon execution, Devin started working in the environment. <strong>Exciting!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cM-0L1efMWh3Z5AYt4kC5g.png" /></figure><p>After about 5 minutes, I received a <strong>DM on Slack</strong> — the first pull request was ready!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*jY9fF205Vg_b2kUGuUD_3A.png" /></figure><h3>Communicating with Devin</h3><p>I could respond directly in the Slack thread or return to the work screen for further interaction. This time, I chose to leave a <strong>GitHub comment</strong> instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*kqvlaHo5EtPpdecJouMPhw.png" /></figure><p>The pull request description was in English, so I asked Devin to rewrite it in Japanese. Devin picked up on my comment and started working again.</p><p>However, this time, there was no response for a while. What could be taking so long?</p><p>When I checked the work environment, I saw Devin <strong>patiently waiting</strong> for the CI process to finish.<br> <em>Adorably diligent…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Nsql-uZGrl-4yjDki-Ncw.png" /></figure><h3>Clarifying Instructions</h3><p>After a while, Devin responded by translating the README.md into Japanese.<br> It turned out my instructions were unclear, so I apologized and rephrased my request more specifically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VKikriviYcgcDcMjI9tI_w.png" /></figure><p>When I asked it to <strong>“Re-request review once you’re done”</strong>, Devin complied perfectly. <strong>Good job!</strong></p><p>Upon confirming that the pull request description was now in Japanese, I gave an <strong>LGTM</strong>. Devin then asked for instructions regarding merging, so I told it: <strong>“Don’t merge on your own.”</strong></p><h3>Session Summary</h3><p>At the end of the session, I asked Devin to summarize the work done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*i_Vm26d_57M_J8yxyHHvdA.png" /></figure><p>It even recorded the timestamps, which was impressive attention to detail.</p><p>Interestingly, the type of direct feedback I gave Devin would probably feel harsh with a human colleague. But Devin remained calm and professional (not that it has a face, but still).</p><p>In fact, I noticed myself naturally using casual language with Devin, even though I typically use formal language at work. Strange, but fascinating.</p><h3>What Devin Learned Today</h3><p>When I ended the session with a <strong>“SLEEP.”</strong> command, Devin prompted me to review what it had learned from this session:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_PZorkXqEZFHlqpt5bJ9Fg.png" /></figure><ul><li><strong>Write pull request descriptions in Japanese, even if the code/documents are in English.</strong></li><li><strong>Send a review request after addressing feedback.</strong></li><li><strong>Devin should never merge pull requests. The owner must do it.</strong></li><li><strong>README.md should not be translated to Japanese unless explicitly instructed.</strong></li></ul><p>I approved the first and third points, which were then added to its <strong>knowledge base.</strong></p><p>The fact that Devin tries to learn and improve felt quite moving. As a developer, I understand how challenging it is to create a user experience where the system gets smarter through interaction.</p><h3>Session Costs</h3><p>Now, for the financial side:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2BwpxsBnxC-pM4zpVfg5ng.png" /></figure><p>This session consumed <strong>2.96 ACUs</strong>.</p><p><strong>1 ACU = $2</strong>, so the total came to around <strong>$6</strong> (~¥1,000).</p><p>Suddenly, the cost felt quite significant when it came out of my own pocket.<br> I’ll need to be mindful of which tasks I delegate moving forward.</p><p>Although Devin was expensive enough that I felt reluctant to let it write this very log entry, I guess I’ll continue writing these myself — for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5de3aff01d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Devin Observation Diary — Day 0]]></title>
            <link>https://medium.com/@daikiteramoto/devin-observation-diary-day-0-a48ea1b0460f?source=rss-6d6d856f5b28------2</link>
            <guid isPermaLink="false">https://medium.com/p/a48ea1b0460f</guid>
            <category><![CDATA[devin]]></category>
            <dc:creator><![CDATA[Daiki Teramoto]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 02:33:46 GMT</pubDate>
            <atom:updated>2025-01-12T02:33:46.906Z</atom:updated>
            <content:encoded><![CDATA[<h3>Devin Logbook — Day 0</h3><blockquote>This article is a translated version of my Japanese blog post, originally published <a href="https://note.com/teramotodaiki/n/n00dde86ff676">here</a>.</blockquote><p>I finally decided to purchase Devin. It’s $500 a month. <a href="https://devin.ai/">https://devin.ai/</a><br> I had been curious about it for a while but hesitated due to the price. However, today, thanks to the generosity of @nishio, I had the chance to try it out, and I was impressed enough to make the purchase.</p><p>So, starting today, I’m beginning a blog titled <strong>“Devin Logbook.”</strong><br> No affiliate links here — just a laid-back chronicle of my experience.</p><h3>“I Want to Add This Repository as a Target for Development”</h3><p>The first thing that surprised me was how tasks are assigned to Devin.<br> I thought I’d have to click through a GUI, but instead, you just mention, <strong>“I want to add this repository as a target for development.”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*MVwLitMNIMH3ZlarwTVs3Q.png" /></figure><p>That was all it took. Devin cloned the repository, read the README, and even ran npm install. It felt like there was someone remote assisting me—it was that seamless.</p><p>The initial authorization was done by the contract holder (@nishio) using GitHub OAuth. For some reasons, the original public repository was forked instead of working directly on the original.</p><h3>“Shigodeki” (Highly Capable)</h3><p>The next impressive thing was how Devin handles troubleshooting. It’s easier to show than explain:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*amAePFIZMfbrwv07h5fE7A.png" /></figure><p>When the canvas package build failed, Devin identified the issue and presented two solutions:</p><ul><li><strong>Use Node.js v18 LTS (current version too new)</strong></li><li><strong>Update the </strong><strong>canvas package</strong></li></ul><p>Devin didn’t blindly update the package, risking further issues, nor did it freeze and ask, <strong>“What should I do now?”</strong> Instead, it presented options for me to decide.<br> This, I thought, is how a <strong>capable professional</strong> should behave.</p><p>By the way, any instructions written in the thread are picked up by Devin. If you write (aside), it won&#39;t be processed, allowing for off-topic discussions.</p><h3>Authentication Error Brings Me Back to Reality</h3><p>Just as I was marveling at Devin’s intelligence, reality struck back.</p><p>When trying to create a Pull Request, an <strong>authentication error</strong> occurred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*sDnzM3-N5cld-MdEqmo_Jw.jpeg" /></figure><p>Although it should work based on GitHub’s setup, it seemed to be a Devin issue. For some reason, retrying solved the problem.</p><p>(Side note: No matter how smart AI gets, handling <strong>authentication and authorization</strong> remains complex. The balance of how much access an AI agent should have is bound to become a significant topic in the future.)</p><h3>LGTM</h3><p>After about an hour of trial and error, Devin completed a task:<br> <strong>Documenting the verification steps in the README.</strong></p><p>In fact, Devin did even more impressive work than I described here, so check the Pull Request if you’re curious.<br> Devin actually performed the steps in a browser before documenting them.</p><p><a href="https://github.com/nishio/hackforplay-common/pull/1">https://github.com/nishio/hackforplay-common/pull/1</a></p><h3>So, How Much Did It Cost?</h3><p>This session lasted about an hour and consumed <strong>6.81 ACUs</strong>.<br> Since 500 USD buys 250 ACUs, this translates to roughly <strong>$13.62</strong> or around <strong>¥2,000</strong>.</p><p>Not exactly cheap, but it enabled me to tackle tasks I had been too busy to handle. Plus, prices will probably drop over time. <em>Maybe?</em></p><p>So, I was all set to fully commit to Devin… until I ran into a strange issue.</p><p>When signing up, I was invited to an organization, which prevented me from creating my own org and subscribing independently.<br> <strong>The “Personal Org” plan doesn’t allow subscriptions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EaphfLnmQPuOAs4NqxqVpw.png" /></figure><p>I’m still waiting for support to clarify this, but hopefully, by tomorrow, I’ll officially become a Devin owner and can start using it as intended.</p><p><strong>Next Up:</strong><br> I should be able to run Devin properly from my own account.<br> I’m embracing the world where <strong>AI handles all development!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a48ea1b0460f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>