<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Codex on yexca'Blog</title><link>https://blog.yexca.net/en/tags/codex/</link><description>Recent content in Codex on yexca'Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>yexca</copyright><lastBuildDate>Sun, 07 Jun 2026 18:42:10 +0900</lastBuildDate><atom:link href="https://blog.yexca.net/en/tags/codex/feed.xml" rel="self" type="application/rss+xml"/><item><title>First Try at Vibe Coding: Accidentally Inhaling a New Digital Drug</title><link>https://blog.yexca.net/en/archives/284/</link><pubDate>Sun, 07 Jun 2026 18:42:10 +0900</pubDate><guid>https://blog.yexca.net/en/archives/284/</guid><description>📢 This article was translated by gemini-3.5-flash A friend strongly recommended Codex to me recently, so I gave it a spin. After trying it myself, I’d call it an “idea extractor.”
Before this, my impression of AI coding was that it could build things, but the resulting code would be a mess to maintain. But after actually getting my hands dirty, I burned through 72M tokens in one go. My ideas kept getting pulled out and turned into reality. It was a massive productivity …</description></item></channel></rss>