Sébastien Cevey

We’re unifying all of our developer offerings under the Claude brand. - Anthropic Platform → Claude Developer Platform - Anthropic API → Claude API - Anthropic Docs → Claude Docs (available at docs.claude.com) - Anthropic Help Center → Claude Help Center (available at support.claude.com) - Anthropic Console → Claude Console (available platform.claude.com and at console.anthropic.com until 12/16/25) You'll see updated naming across our sites and documentation, but your technical implementation stays the same.

Vibe code is legacy code @karpathy coined vibe coding as a kind of AI-assisted coding where you "forget that the code even exists" We already have a phrase for code that nobody understands: legacy code Legacy code is universally despised, and for good reason. But why? You have the code, right? Can't you figure it out from there? Wrong. Code that nobody understands is tech debt. It takes a lot of time to understand code enough to debug it, let alone introduce new features without also introducing bugs Programming is fundamentally theory building, not producing lines of code. This is why we make fun of business people who try to measure developer productivity in lines of code When you vibe code, you are incurring tech debt as fast as the LLM can spit it out. Which is why vibe coding is perfect for prototypes and throwaway projects: It's only legacy code if you have to maintain it! I vibe code happily all the time. Most often for small apps that I don't need to maintain. I'm a big fan, have at it! Vibe coding is on a spectrum of how much you understand the code. The more you understand, the less you are vibing Simply by being an engineer and asking for a web app with a persistent database, you are already vibing less than than a non-programmer who asks for an "app" without understanding the distinction between a web app and a native app, or how persistent data storage works The worst possible situation is to have a non-programmer vibe code a large project that they intend to maintain. This would be the equivalent of giving a credit card to a child without first explaining the concept of debt You'll end up spending a lot of money and getting a large, buggy, legacy code base. If you don't understand the code, your only recourse is to ask AI to fix it for you, which is like paying off credit card debt with another credit card At Val Town, we built Townie, an AI assistant that agnatically reads & writes code, runs it, views the logs, and keeps iterating until it's done. It's is an awesome tool for vibe coding. I heartily recommend it to folks who understand these tradeoffs. I use it to vibe code sometimes. Other times I keep in on a tight leash as it makes surgical edits to a project I care about If you know any non-programmers spending thousands of dollars vibe coding their billion dollar app idea today, warn them that vibe coding is not going to get them where they want to go. They're going to have to learn to use their human eyes to read the code 😱, and that sometimes it's easier to start over with building a well-written code base from scratch than to fix a legacy one that nobody understands