Last month I dropped a desperate little plea for help in this space, asking people to email me any good advice and/or strong opinions they happened to have on the topic of buying software. I wasn’t really sure what to expect — desperate times, desperate measures — but holy crap, you guys delivered. To 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 is seeking community input for the second edition of her observability book, specifically requesting experiences and opinions on vendor migrations, cost management strategies for traditional three-pillar architectures, observability team structures, OpenTelemetry adoption decisions, and build-vs-buy considerations. She emphasizes that vendor engineering and software procurement are high-leverage activities requiring deep technical expertise, and shares specific questions about managing observability tools at scale, including migration playbooks, cost control tactics, and instrumentation automation.

Got opinions on observability? I could use your help (once more, with feeling)

Why I’m excited about the software buying chapter (& you should be too)