Developer Community Metrics — Vocabulary and Discussion
Learn vocabulary for measuring and discussing developer community health.
0 / 14 completed
1 / 14
What is 'DAU/MAU ratio' in community health metrics?
DAU/MAU ratio (Daily Active Users / Monthly Active Users) measures stickiness — how often monthly members return daily. A ratio of 0.2 means active members visit about 6 days per month on average.
2 / 14
What is 'time to first response' in community health?
Time to first response measures community responsiveness — how quickly questions get answered. High response time indicates community health and can predict member retention.
3 / 14
What is 'contributor retention rate' in open source communities?
Contributor retention rate measures how many first-time contributors return to contribute a second time — a key indicator of contributor experience quality and community welcoming culture.
4 / 14
What is 'Net Promoter Score' (NPS) applied to developer communities?
Developer community NPS asks members to rate (0–10) how likely they are to recommend the community. Promoters (9–10) minus Detractors (0–6) = NPS. Tracks community satisfaction trends over time.
5 / 14
What is 'question resolution rate' in community forums?
Question resolution rate measures what percentage of questions asked in the community get a useful, accepted answer — indicating how well the community serves its members' needs.
6 / 14
PR Description
During a code review, Sarah noticed a significant increase in the number of users reporting issues with a recently deployed feature. She's reviewing David's PR and sees this message:
"Implemented new API endpoint for user profile updates. Initial metrics show a 30% spike in error rates related to authentication."
Which of the following terms best describes the issue David is reporting, and what metric is he *implicitly* highlighting?
This scenario focuses on 'volume' as a key community metric. While 'high volume' accurately describes the situation – a sudden increase in reported errors—David is implicitly reporting a problem with the *impact* of the new feature on user experience. The goal isn't just to note that many users are having issues, but to understand how that volume translates into real-world problems and potential negative feedback within the developer community. Options A, C, and D misinterpret the core issue; David is indicating a problem with the *quantity* of reports, not the overall adoption or severity.
7 / 14
PR Description
During a code review, Sarah noticed a significant increase in the number of users reporting issues with a recently deployed feature. She's reviewing David's PR and sees this message:
"Implemented new API endpoint for user profile updates. Initial metrics show a 30% spike in error rates related to authentication."
Which of the following terms best describes the issue David is reporting, and what metric is he *implicitly* highlighting?
This scenario focuses on 'volume' as a key community metric. While 'high volume' accurately describes the situation – a sudden increase in reported errors—David is implicitly reporting a problem with the *impact* of the new feature on user experience. The goal isn't just to note that many users are having issues, but to understand how that volume translates into real-world problems and potential negative feedback within the developer community. Options A, C, and D misinterpret the core issue; David is indicating a problem with the *quantity* of reports, not the overall adoption or severity.
8 / 14
PR Description
During a code review, Sarah noticed a significant increase in the number of users reporting issues with a recently deployed feature. She's reviewing David's PR and sees this message:
"Implemented new API endpoint for user profile updates. Initial metrics show a 30% spike in error rates related to authentication."
Which of the following terms best describes the issue David is reporting, and what metric is he *implicitly* highlighting?
This scenario focuses on 'volume' as a key community metric. While 'high volume' accurately describes the situation – a sudden increase in reported errors—David is implicitly reporting a problem with the *impact* of the new feature on user experience. The goal isn't just to note that many users are having issues, but to understand how that volume translates into real-world problems and potential negative feedback within the developer community. Options A, C, and D misinterpret the core issue; David is indicating a problem with the *quantity* of reports, not the overall adoption or severity.
9 / 14
PR Description
During a code review, Sarah noticed a significant increase in the number of users reporting issues with a recently deployed feature. She's reviewing David's PR and sees this message:
"Implemented new API endpoint for user profile updates. Initial metrics show a 30% spike in error rates related to authentication."
Which of the following terms best describes the issue David is reporting, and what metric is he *implicitly* highlighting?
This scenario focuses on 'volume' as a key community metric. While 'high volume' accurately describes the situation – a sudden increase in reported errors—David is implicitly reporting a problem with the *impact* of the new feature on user experience. The goal isn't just to note that many users are having issues, but to understand how that volume translates into real-world problems and potential negative feedback within the developer community. Options A, C, and D misinterpret the core issue; David is indicating a problem with the *quantity* of reports, not the overall adoption or severity.
10 / 14
David posted this message in Slack after a spike in support tickets related to the new API endpoint:
"We've seen a surge in requests for help with authentication. Users are reporting errors when trying to access /v1/users. Thinking of rolling back the recent changes."
This situation highlights the importance of monitoring API usage and support tickets. A sudden spike in 'error requests' points to an issue with the endpoint itself – likely related to changes made by David – not simply a high volume of users. Ignoring it would delay critical debugging. The key metric here is user experience, not raw request numbers.
11 / 14
Liam is presenting community health metrics to the product team. He explains that 'velocity' refers to: "How quickly we can deliver features."
'Velocity' in a developer community context is often misunderstood. It's *not* just about commits or adoption rates. It specifically measures the speed of development output—how quickly code changes are being deployed. Using 'adoption rate' would be measuring user behavior, not development efficiency.
12 / 14
Maria is drafting a PR description for a small bug fix related to handling null values in the data parsing module. She wants to accurately convey the impact of her change. Which statement best describes her approach?
A good PR description should clearly articulate *what* problem was solved and *how*. Maria's response accurately describes the bug fix – specifically addressing the potential crash caused by null values. Options A and B are too vague; option C is a technically correct but less informative explanation of the solution, while D completely misses the core issue.
13 / 14
Ben, during a standup meeting, reports:
'Our community engagement score is down 15% this week. We're seeing fewer active users on the forums and less participation in discussions.' What does a 'community engagement score' most likely represent?
A 'community engagement score' is rarely a single calculation. It's typically a *composite metric* designed to give a holistic view of how actively users are participating within the community. This includes various indicators—forum activity, issue submissions, and contributions – weighted appropriately to reflect their importance.
14 / 14
Chloe is analyzing API response data for a developer community platform. She notices that the average '404 Not Found' error rate for requests to the documentation endpoint is consistently high (7%). What does this primarily indicate?
A consistently high '404 Not Found' error rate suggests an issue with the API itself – specifically how it handles requests to the documentation endpoint. This could be misconfigured routes, server problems serving files, or even a problem with DNS resolution. User behavior (option C) is less likely, and while high traffic can *contribute* to delays, it doesn't directly cause 404 errors.
What does the "Developer Community Metrics — Vocabulary and Discussion" exercise practise?
Learn vocabulary for measuring and discussing developer community health.
How many questions are in this exercise?
This exercise has 14 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Developer Community Management category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Developer Community Metrics — Vocabulary and Discussion" part of a larger series?
Yes — it's one exercise in the Developer Community Management category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Developer Community Management category page for related exercises, or browse the main Exercises hub for other IT English topics.