korrents
Charity Majors

What Charity Majors thinks about software quality

@charity-majors · 56 positions · 1 change of mind · On ppll ↗

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.

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.

Filter software quality · Newest first
Topic
All 56management 14hiring 6code generation 3software quality 3vibe coding 3coding agents 2AI agents 1AI and human skill 1AI and jobs 1
7 more topics
AI slop 1creativity 1innovation 1motivation 1product management 1team size 1writing 1
Sort
NewestOldest

Only Charity Majors on software quality. See everyone on software quality

3 dated positions, 2022 to 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 readingLines of code are the wrong artifact to review; what we should be storing and reviewing is an architecture that generates the code to spec.

    Their wordsLike that just does not seem like the ideal artifact. We should be able to store them somewhere. We should be able to have architecture diagrams that we can review and discuss that generate that code to spec.

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

  3. Our readingIf engineers do not hold themselves to a high standard and build efficiently, somebody else will come along and impose it on them.

    Their wordsIf we don't do it ourselves, meaning hold ourselves to a high standard, build with efficiency, constantly be like trying to get better, if we don't do it ourselves, someone will come and do it to us.

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

  4. 4 years earlier

  5. Our readingA permanently painful on-call rotation is a five-alarm emergency, not a normal cost of owning code in production.

    Their wordsBeing on call should not be a constant cycle of things breaking down and firefighting, or alerts going off at all hours. This is not ‘normal.’ These are telltale signs of a fragile system and lack of alert discipline.

    ↗Why On-Call Pain Is A Sociotechnical Problemcharity.wtf 1st of 5 in this piece