<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Opinion on Khang Nghiem</title><link>https://www.khangnghiem.com/tags/opinion/</link><description>Recent content in Opinion on Khang Nghiem</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.khangnghiem.com/tags/opinion/index.xml" rel="self" type="application/rss+xml"/><item><title>When Vibe Coding Hits a Wall</title><link>https://www.khangnghiem.com/post/vibe-coding-hits-a-wall/</link><pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.khangnghiem.com/post/vibe-coding-hits-a-wall/</guid><description>&lt;p&gt;&lt;em&gt;This post is a discussion of &lt;a href="https://qiita.com/aakashkavuru101/items/1c39acd71dbead4f6d99"&gt;AI-Driven Development: From Vibe Coding to Structured Methodologies&lt;/a&gt; by Aakash Kavuru. Worth reading in full.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Vibe coding is fun. You describe what you want, the AI writes it, you ship. It works great for the first two weeks. Then the codebase grows, the AI starts misunderstanding context, and you spend more time fighting the output than building.&lt;/p&gt;
&lt;p&gt;This is not an AI problem. It is a documentation problem you ignored because the AI made it easy to ignore. The original article puts it well: the root cause of almost every failure in AI-driven development is that &amp;ldquo;what needs to be created remains undocumented.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Software is Getting Cheap. Now What?</title><link>https://www.khangnghiem.com/post/software-getting-cheap/</link><pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate><guid>https://www.khangnghiem.com/post/software-getting-cheap/</guid><description>&lt;p&gt;A solo developer with Claude and Vercel can ship in a weekend what took a team of five six months to build. The software is not worse. Sometimes it is better.&lt;/p&gt;
&lt;p&gt;This post is not about whether AI will replace engineers. That question is mostly a distraction. The more interesting question is: what changes when the cost of building software drops toward zero, and what does that mean for you specifically?&lt;/p&gt;</description></item></channel></rss>