What Charity Majors thinks about team size

@charity-majors · 50 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 team size · Newest first

Topic

All 50team size 1management 14hiring 6code generation 3software quality 3vibe coding 3coding agents 2AI agents 1AI and human skill 1

7 more topics

AI and jobs 1AI slop 1creativity 1innovation 1motivation 1product management 1writing 1

Sort

NewestOldest

Only Charity Majors on team size. See everyone on team size

1 dated position, 2022, in their own words. Our reading of what Charity Majors has said — not written or endorsed by them.

1 position so far — this page is not yet offered to search engines.

1. 30 Jun 2022

   Our readingA sustainable on-call rotation needs seven or eight engineers.

   Their wordsThe ideal on-call rotation has seven to eight people; five people is a bare minimum.

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