https://www.khangnghiem.com/tags/ai/Recent content in Ai on Khang NghiemHugoenWed, 24 Jun 2026 00:00:00 +0000https://www.khangnghiem.com/post/claude-code-microservices/Wed, 24 Jun 2026 00:00:00 +0000https://www.khangnghiem.com/post/claude-code-microservices/<p>Claude Code works great on a single service. The moment you have ten services each in their own git repository, it stops knowing where it is.</p> <p>It suggests calling the orders database from the user-service. It forgets your team uses Kafka for async events. It recommends patterns from the wrong stack. Not because Claude is bad, but because it has no map.</p> <p>The fix is giving it one.</p> <h2 id="the-approach-import-from-a-shared-repo">The Approach: <code>@import</code> from a Shared Repo</h2> <p>Claude Code supports importing other files inside <code>CLAUDE.md</code> using the <code>@path/to/file</code> syntax. This lets you pull shared standards from a dedicated versioned repo directly into each service&rsquo;s context.</p>https://www.khangnghiem.com/post/vibe-coding-hits-a-wall/Wed, 10 Jun 2026 00:00:00 +0000https://www.khangnghiem.com/post/vibe-coding-hits-a-wall/<p><em>This post is a discussion of <a href="https://qiita.com/aakashkavuru101/items/1c39acd71dbead4f6d99">AI-Driven Development: From Vibe Coding to Structured Methodologies</a> by Aakash Kavuru. Worth reading in full.</em></p> <hr> <p>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.</p> <p>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 &ldquo;what needs to be created remains undocumented.&rdquo;</p>https://www.khangnghiem.com/post/software-getting-cheap/Wed, 13 May 2026 00:00:00 +0000https://www.khangnghiem.com/post/software-getting-cheap/<p>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.</p> <p>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?</p>