korrents

What Charity Majors thinks about vibe coding

@charity-majors · 50 positions · 1 change of mind

Co-founder and CTO of Honeycomb, previously an infrastructure engineer at Parse, Facebook and Linden Lab. Co-author of "Database Reliability Engineering" and "Observability Engineering". Writes at charity.wtf about on-call, hierarchy, hiring and the engineer/manager pendulum.

Everything they publish, on ppll ↗

Charity Majors 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.

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

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

  1. Our readingThere is no point arguing about whether or when engineers will ship code they have not read; the only useful question is what it would take.

    Their wordsWhat I was saying in that piece though was, I think we were right to be skeptical that time. But now, I see the same thing playing out with would you be willing to ship it some code you didn't read? There's no point in arguing about if it will happen or when it will happen. Talk about what it would take.

    ↗Stop being skeptical about AI for development with Charity Majorsyoutube.com 4th of 26 in this recording

  3. Our readingIf you are not going to read the generated code, what you need is conformance testing: proof that it performs within the boundaries of the code it replaced.

    Their wordsOkay, if I'm not going to read this code, how do I know it's going to perform within boundaries of the last code that I generated? That is conformance testing.

    ↗Stop being skeptical about AI for development with Charity Majorsyoutube.com 11th of 26 in this recording

    code generation

  5. Our readingTrust is an account: whatever you withdraw from it by not reading the code has to be built back up somewhere else.

    Their wordsIf you're debiting from this trust account in the creation of the code, it has to get built up somewhere else.

    ↗Stop being skeptical about AI for development with Charity Majorsyoutube.com 12th of 26 in this recording