I'm not sure whether to say "thank you" or "HOW COULD YOU DO THIS TO ME", but this one goes out to all the people who sent me advice on buying software last fall. This is the second in a two-part episode. The first part ended on a ✨cliffhanger!!!✨ — so if you missed the…

Charity's platform is a central hub for nonprofit organizations, volunteers, and philanthropists, offering insights into charitable initiatives, fundraising strategies, and social impact projects. Through articles, success stories, and fundraising guides, Charity offers insights into effective nonprofit management, donor engagement, and community outreach efforts. Readers can learn about nonprofit governance, grant writing, and advocacy campaigns to support causes they care about and make a positive difference in the world.

Charity

Charity Majors shares the story of scrapping and rewriting a major section of her observability book after community feedback revealed she had written tactical advice for engineering teams when the real problem was strategic misalignment at the leadership level. After soliciting input from SREs, CTOs, VPs, and CISOs, she discovered that most observability failures stem from broken buying processes and lack of shared vocabulary between engineering and business stakeholders — not implementation challenges. The rewritten Part 6, 'Observability Governance,' is now structured for technical decision-makers and uses systems thinking language instead of jargon, covering topics from making the business case for observability to vendor partnerships and build-vs-buy decisions. The post also argues that observability is more critical than ever in an AI-native world, since organizational learning speed — enabled by observability — is now the primary constraint on engineering productivity.

First I wrote the wrong book, then I wrote the right book (xpost)

In which I finally listen to the advice I asked for

Part 6: “Observability Governance” (v2)