@karpathy 8/ Rambling lowers the cost of providing context.
Dialogue goes one step further: it improves the context before implementation starts.
Perhaps the future interface for coding agents is not a better prompt box, but a short design conversation.
@karpathy 1/ I like the idea of “rambling” into an AI for 5–10 minutes instead of writing a structured prompt.
But I think there is an even more useful version of this workflow: not a monologue, but a voice conversation.
@karpathy 7/ In this model, the voice assistant acts almost like a product manager, architect, and rubber-duck debugging partner before the coding agent begins changing files.
This could prevent a lot of confidently implemented but incorrectly understood tasks.
@karpathy 6/ That package can then be handed directly to Codex or another coding agent.
So the workflow becomes:
voice discussion → collaborative task discovery → structured specification → coding agent → review
@karpathy 5/ At the end, the model turns the entire conversation into an implementation package:
— objective and business context
— functional requirements
— constraints and non-goals
— architecture decisions
— open questions and risks
— acceptance criteria
— implementation plan
@karpathy 4/ The important part is that the model is not merely transcribing or restructuring my thoughts.
It is helping me discover what the task actually is.
The specification emerges from the dialogue.
@karpathy 3/ So instead of recording one long ramble, I could discuss the task with a voice model.
I explain what I want in my own words. The model asks clarifying questions, challenges assumptions, points out missing cases, and suggests alternative approaches.
@karpathy 2/ When I start a new software task, I rarely understand it well enough to write a perfect specification immediately.
I usually have a goal, some constraints, fragments of context, and several ideas that may still contradict each other.
Switched to GPT-5.6 Sol because it performs better on long, complex engineering tasks.
For Python backend, LLM integrations, agent systems, and Codex, it follows instructions more reliably and makes fewer incorrect assumptions.
Less time fixing AI. More time building.
we've seen nothing yet! hosted a 9-13 yo vibe-coding event w. @robertkeus this w-e (h/t @antonosika@LovableBuild)
takeaway? AI is unleashing a generation of wildly creative builders beyond anything I'd have imagined
and they grow up *knowing* they can build anything!
DEMO TIME! Customer service:
Help a customer with a question about an order that did not arrive. This time the customer accidentally did not write the order ID correctly 😯
Somewhat interesting advertising choice from Anthropic, comparing their newly released Claude 3 to GPT-4 on release (March 2023).
According to Promptbase's benchmarking, GPT-4-turbo scores better than Claude 3 on every benchmark where we can make a direct comparison.
Had a nice conversation with #ChatGPT and #DiffusionBee
It built me this application just by friendly asking for it and iterating, starting from a random recipe string generator
All additional features were suggested and implemented by ChatGPT itself
NCA! (No Cooking Advise)