Curated topic · 12 ARTICLES
Explore practical Vibe Coding articles grounded in clear explanations and engineering tradeoffs.
Latest articles
Vibe Coding mishaps are decided when you write the first rule file, not when you read the code. Here are five rules for CLAUDE.md and .cursorrules covering security, duplication, architecture, completion criteria, and scope, with example wording.
Read articleSix security checks to complete before publishing your app link. Assuming attackers cast a bot-driven net without choosing targets, this covers the doors commonly breached in vibe-coding apps: RLS, authorization checks, input validation, and more.
Read article"I woke up to a cloud bill of several million won." Posts like this appear regularly in vibe-coding communities, and they are enough to make anyone's stomach drop. A hobby app has returned a month's salary as an invoice. The scary part is that this is not an accident limited to unusually careless people. If you do not understand the billing model, it can happen to anyone. Billing…
Read articleThe AI covered in the previous seven installments was ultimately a “ask-and-answer” tool. People drove the conversation: refining questions, providing materials, and verifying answers. But the next step the AI industry has pursued for the past two years is different in kind. AI agents do not just converse—they take on the work itself.…
Read article“I didn’t touch a single line of code, but the app that worked fine yesterday doesn’t work today.” It’s the most common complaint in vibe-coding communities—and one of the most mysterious situations. It feels like a ghost story, but the suspects are actually limited. Investigate them in order, and you can usually catch the culprit before noon…
Read articleAsking AI to build a website is easy now. The real struggle starts afterward—when you show the finished screen and say, “This button looks a little odd.”
Read articleWhen red error messages cover the screen, your heart sinks. The English is dense, full of unfamiliar words, and seems not to tell you what went wrong. So many vibe coders close the message without reading it and tell AI, "It doesn't work—fix it." Then AI starts changing the wrong parts.
Read articleThe app is complete. It runs perfectly on my computer. I copy localhost:3000 from the address bar to show it off to a friend, but they reply, "It won't open." I finally deploy it, only to find that the app that worked locally now throws errors on the internet.
Read articleVibe coding inevitably brings this day. You ask AI to add one feature to an app that worked fine yesterday, and it changes things everywhere until the entire app stops working. Even if you ask, "Put it back the way it was," AI cannot restore it precisely. It changed twenty places, and it does not know which one is broken…
Read articleIn Part 1, I compared an app to a restaurant: dining area (frontend), kitchen (backend), and storage (DB). This time, we cover the topic most likely to cause trouble in vibe coding: APIs—and API keys. Everyone has seen “Never expose your key,” but few explain what the key is, where it lives, or what happens when it leaks. This article covers it all.
Read articleMore people are building apps by describing them to AI. Tell tools like Cursor, Claude Code, or v0, "Build this service," and a working app appears. But after building it, many hit the same wall: the app runs, yet they do not know what AI actually created…
Read articleDeveloping by pressing Accept All without reading AI-generated code is what we now call “vibe coding.” It gets you started astonishingly fast, and many say it is hard to go back once you try it. Still, know in advance where and how the cost of not reading code will come due.
Read article