korrents
Thorsten Ball

What Thorsten Ball thinks about vibe coding

@thorsten-ball · 70 positions · 2 changes of mind · On ppll ↗

Co-founder of Amp and co-host of the Raising an Agent podcast. Wrote Writing an Interpreter in Go.

Thorsten Ball did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter vibe coding · Newest first
Topic
All 70vibe coding 3AI agents 13software quality 11LLMs 10developer tools 9coding agents 8simplicity 5agency 4design 4
24 more topics
AI and human skill 3AI and jobs 3innovation 3Ruby 3TypeScript 3writing 3ambition 2optimism 2remote work 2software performance 2team size 2AI slop 1code generation 1compilers 1documentation 1Europe 1Google 1humility 1infrastructure 1MCP 1open source 1patience 1product management 1startups 1
Sort
NewestOldest

Only Thorsten Ball on vibe coding. See everyone on vibe coding

3 dated positions, 2026, in their own words. Our reading of what Thorsten Ball has said — not written or endorsed by them.

3 positions so far — this page is not yet offered to search engines.

  1. Our readingTell a coding agent what you want rather than how to do it; you will often get better results.

    Their wordsDescribe What you want, now How you'd do it. You'll often get better results.

    ↗How I work with Agentsx.com 3rd of 14 in this piece

  3. Our readingOnly code with a high blast radius needs human review, such as a few central files and database migrations; style choices and even duplication no longer matter.

    Their wordsReview only code with high blast radius. There are <5 central files -- those I review. Database migrations, yes. Closure vs. class, a neater type, variable names, even duplication: I don't care anymore.

    ↗How I work with Agentsx.com 14th of 14 in this piece

  4. 5 weeks earlier

  5. Our readingIn the future, humans will not find bugs in model-produced code in reasonable time and will only review system composition, not via PRs or line-by-line review.

    Their wordsin the future, humans won’t find a bug or an issue with the code produced by a model, at least not in a reasonable time. Humans will only review the system and its composition, but it won’t be in PRs and it won’t be by looking through every line of the code.

    ↗What I believe about the future of software developmentthorstenball.com 1st of 15 in this piece