Vibe coding in prod | Code w/ Claude
- Source
- youtube.com
- Author
- Anthropic
- Date
Context
In a talk at Code w/ Claude, Eric, a researcher at Anthropic who works on coding agents, proposes how to vibe code, meaning to build while not reading the code, in production responsibly. Eric's rule is to forget the code exists but not the product. You can trust work you cannot read when you can verify it through something you do understand, as a CTO writes acceptance tests for an expert or a product manager uses the finished product.
Eric makes one exception: technical debt, because Eric knows of no good way to check it without reading the code. So Eric suggests applying this approach to leaf nodes, parts of a system that nothing else depends on, while engineers still understand the core architecture. Eric also says to spend 15 to 20 minutes gathering for Claude before starting. These are recommendations from a speaker's view.
- context window — The maximum amount of text a model can consider at once — its working memory for the current conversation or task.
- vibe coding — Building software by describing what you want to an AI in plain language and steering the result, instead of writing every line yourself.
Checking sign-in…
Loading comments…






