Anonymize quote attributions to reduce identifiability

- Remove "programming language committee chair" from distinguished engineer
- Simplify "Founder and CEO" to "Executive at a developer tools company"
- Remove specific expertise from research software engineer

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: nikomatsakis

content/what-do-people-love-about-rust.md

@@ -42,11 +42,11 @@ At the other end of the spectrum, people doing embedded development or working a
 
 > "Rust was that replacement for C I'd been looking for forever." -- Backend engineering company founder specializing in financial services
 
-> "If you're going to write something new and you do kind of low-level systemsy stuff, I think Rust is honestly the only real choice." -- Distinguished engineer and programming language committee chair
+> "If you're going to write something new and you do kind of low-level systemsy stuff, I think Rust is honestly the only real choice." -- Distinguished engineer 
 
 Many people cite the importance of Rust's **supportive tooling**, which helps them get up and going quickly, and in particular the compiler's error messages:
 
-> "I think a big part of why I was able to succeed at learning Rust is the tooling. For me, getting started with Rust, the language was challenging, but the tooling was incredibly easy." -- Founder and CEO of company creating developer tools
+> "I think a big part of why I was able to succeed at learning Rust is the tooling. For me, getting started with Rust, the language was challenging, but the tooling was incredibly easy." -- Executive at a developer tools company
 
 > "The tooling really works for me and works for us. The number one way that I think I engage with Rust is through its tooling ecosystem. I build my code through Cargo. I test it through Cargo. We rely on Clippy for everything." -- Embedded systems engineer working on safety-critical robotics
 
@@ -164,7 +164,7 @@ We mentioned earlier how Rust's extensibility is part of how it achieves versati
 
 > "The crates to use are sort of undiscoverable. There's a layer of tacit knowledge about what crates to use for specific things that you kind of gather through experience and through difficulty. Everyone's doing all of their research." -- Web developer and conference speaker working on developer frameworks
 
-> "Crates.io gives you some of the metadata that you need to make those decisions, but it's not like a one stop shop, right? It's not like you go to crates.io and ask 'what I want to accomplish X, what library do I use'---it doesn't just answer that." -- Research software engineer with expertise in 2D graphics and font technologies
+> "Crates.io gives you some of the metadata that you need to make those decisions, but it's not like a one stop shop, right? It's not like you go to crates.io and ask 'what I want to accomplish X, what library do I use'---it doesn't just answer that." -- Research software engineer
 
 The Rust org has historically been reluctant to "bless" particular crates in the ecosystem. But the reality is that some crates are omnipresent. This is particular challenging for new users to navigate: