~/blog · filtered by category

vibe.

12 entries filed under this signal. ← back to all entries

[blog/category/vibe] · reverse chronological$ ls -la --filter=vibe

2026-07-20vibeWhen to add tests and architecture to an AI-built projectNot on day one, not never. The right moment is a signal you can actually watch for, and it is the same signal for both.#vibe-coding#testing#architecture#ai-coding#technical-debt#paelladoc8 min./read →2026-07-20vibeWhat is vibe coding? (and where it stops working)Karpathy named it: you describe what you want and let the model write the code. It is a real technique with a real edge. This is both.#vibe-coding#ai-coding#what-is-vibe-coding#agentic-development#prototype-to-product#paelladoc7 min./read →2026-07-20vibeVibe coding vs AI-assisted engineering: the line that mattersSame tools, same models, same speed. The line between the two is not the code you generate. It is whether you accept it without verifying it.#vibe-coding#ai-assisted-engineering#ai-coding#verification#spec-driven-development#paelladoc7 min./read →2026-07-20vibeFrom vibe coding to production: the bridge nobody explainsYou described an app and got one. Now real people use it and you have to keep it alive. This is the crossing from prototype to product, stage by stage.#vibe-coding#prototype-to-product#ai-coding#technical-debt#spec-driven-development#paelladoc10 min./read →2026-07-20vibeVibe coding debt: what you actually owe and when it's dueThe interest on vibe-coded software is real, but it is not one number. It is three separate debts with three different due dates.#vibe-coding#technical-debt#ai-coding#maintainability#verification#paelladoc9 min./read →2026-07-20vibeThe security holes vibe coding leaves behindGenerated code that nobody reviewed tends to leak in the same three places. None of them require a rewrite to close, but all of them require you to look.#vibe-coding#security#ai-coding#input-validation#dependencies#paelladoc8 min./read →2026-07-20vibeThe 90-day reckoning: why vibe-coded apps break at month 3The pattern is almost on a schedule. It runs great for weeks, then somewhere around the third month the same app that felt magical becomes impossible to change.#vibe-coding#technical-debt#ai-coding#prototype-to-product#maintainability#paelladoc6 min./read →2026-07-20vibeYou shipped code you can't read. Now what?The quiet panic of vibe coding: the app is live, people use it, and you cannot follow a single file. This is the way out, and it is not learning to read every line.#vibe-coding#ai-coding#codebase-understanding#maintainability#prototype-to-product#paelladoc6 min./read →2026-07-20vibeScared to touch it: turning fear of your own codebase into a safety netThe fear is information. It is telling you exactly where you have no safety net. Follow it, and it becomes a map of what to build.#vibe-coding#testing#characterization-tests#ai-coding#verification#paelladoc8 min./read →2026-07-20vibeYour Lovable prototype is now the product: surviving the promotionNobody decided to ship the prototype. Users just started depending on it. Here is how to promote it without the rewrite you keep threatening.#vibe-coding#prototyping#production#ai-coding#product-development#paelladoc7 min./read →2026-07-20vibeFoundations under the house of cards: fixing a vibe-coded app without a rewriteEveryone tells you to rewrite it properly. You don't have to. You can pour foundations under a running app, one load-bearing piece at a time.#vibe-coding#technical-debt#characterization-tests#spec-driven-development#maintainability#paelladoc7 min./read →2026-07-20vibeEvery new feature breaks an old one: the missing contractYou add feature six and feature two stops working. It is not carelessness. It is a missing contract between the parts, and agents make it worse.#vibe-coding#features-breaking-features#spec-as-contract#regression#ai-coding#paelladoc6 min./read →

— end of log · 12 entries in vibe —