Skip to content

Commit eea4da7

Browse files
authored
Update content/lessons-learned-from-the-rust-vision-doc-process.md
1 parent dc17822 commit eea4da7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/lessons-learned-from-the-rust-vision-doc-process.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ One of the first things we did in starting out with the vision doc was to meet w
4242

4343
## Step 1: Broad-based survey
4444

45-
Before embarking on individual interviews, we wanted to get a broad snapshot of Rust usage. We also wanted to find a base of people that we could talk to. We created a survey that asked a few short "demographic" questions -- e.g., where does the respondent live, what domains do they work on, how would they rate their experience -- and some open-ended questions about their journey to Rust, what kind of projects they feel are a good fit for Rust, what they found challenging when learning, etc. It also asked for (optional) contact information.
45+
Before embarking on individual interviews, we wanted to get a broad snapshot of Rust usage. We also wanted to find a base of people that we could talk to. We created a survey that asked a few short "demographic" questions -- e.g., where does the respondent live, what domains do they work on, how comfortable they feel writing code in Rust -- and some open-ended questions about their journey to Rust, what kind of projects they feel are a good fit for Rust, what they found challenging when learning, etc. It also asked for (optional) contact information.
4646

4747
We got a LOT of responses -- over 4200! Analyzing this much data is not easy, and we were very grateful to [Kapiche](https://www.kapiche.com/), who offered us free use of their tool to work through the data. ❤
4848

0 commit comments

Comments
 (0)