5 exercises on developer experience and productivity vocabulary.
0 / 5 completed
1 / 5
What is the SPACE framework for developer productivity?
SPACE framework (Forsgren, Storey, et al., 2021 — ACM Queue): five dimensions: Satisfaction and wellbeing: do developers feel good about their work, tools, team? Measured by: surveys, NPS, engagement scores. Performance: outcomes of work — does the code do what it should? Measured by: quality metrics, reliability, customer outcomes. Activity: volume of actions (PRs, commits, deploys). Useful for understanding patterns, not for judging individuals. Communication and collaboration: effectiveness of information sharing and teamwork. Efficiency and flow: ability to work without interruption or delays. Measured by: cycle time, WIP, interruptions. Key insight: measure 2-3 dimensions from different perspectives (individual, team, organizational), not just activity metrics.
2 / 5
What is developer toil and why does it matter?
Toil (Google SRE definition): manual, repetitive, automatable, tactical, without enduring value, scales with service growth. Examples: manually restarting services, updating config files by hand, approving routine dependency updates, manually running pre-deployment checklists, copy-pasting data between systems. Why it matters: SRE teams target <50% toil. Above that, morale drops and engineering velocity falls — no time for systemic improvements. Measuring toil: time tracking in weekly surveys, categorize as "toil" vs "project work" vs "overhead". Reducing toil: automate the most frequent tasks first (80/20 rule), build self-service tooling, create runbooks that reduce cognitive load if full automation isn't yet possible. Toil budget: allocate explicit capacity for toil reduction each quarter.
3 / 5
What are DORA metrics in the context of developer experience?
DORA metrics (Google DORA research, Forsgren/Humble/Kim): from the "Accelerate" book. Four metrics: Deployment Frequency: elite teams deploy multiple times/day; low performers monthly or less. Lead Time for Changes: commit → production. Elite: <1 hour. Low: >6 months. Change Failure Rate: % of deploys causing incidents. Elite: 0-15%. Low: 46-60%. Mean Time to Restore (MTTR): how long to recover from incidents. Elite: <1 hour. Low: 1 week+. Key finding: elite performers are BOTH faster AND more reliable — speed and quality reinforce, not trade off. DX teams use DORA metrics to identify bottlenecks in the delivery pipeline.
4 / 5
What is a friction log in developer experience research?
Friction log: a structured walkthrough. Someone — ideally a developer new to the system (highest friction sensitivity) or the DX team — attempts a task (set up the dev environment, deploy a new service, debug a production issue) and writes down every point of friction: confusing docs, unclear error messages, missing steps, too many manual steps, broken links, context switching. Format: task description + step-by-step journal + screenshots + "what I expected vs what happened". Output: prioritized list of pain points. High-value because it surfaces invisible friction that experienced developers no longer notice (habituation). Complements quantitative metrics (cycle time) with qualitative context (where does time go?).
5 / 5
What is flow state and how do developer experience teams protect it?
Flow state (Csikszentmihalyi): a psychological state of deep focus where complex problem-solving is most effective. Takes ~15-20 minutes to enter after an interruption. Interruptions cost much more than their duration. Developer flow research: developers average 1-2 hours of uninterrupted focus per day in typical office environments. How DX teams protect flow: Async-first culture: Slack is async — no expectation of immediate response. Focus blocks: no-meeting mornings, "maker schedules". Fast tooling: slow CI (<10 min) is less interrupting than slow CI (30+ min — context switch to other work). Batch notifications: PR review requests batched, not real-time. Incident paging discipline: page only when humans need to act now. Cognitive load theory: working memory is limited. High-complexity environments (complex dev setup, many tools, fragmented documentation) exhaust cognitive capacity before the real work begins.
These modules build the same on-the-job skills as Developer Experience
— work through them together for a fuller vocabulary set.
Developer Productivity— useful for Developer experience (DX) vocabulary (Technical Writer)
Frequently Asked Questions
What does the "Developer Experience" vocabulary exercise cover?
This exercise tests real IT vocabulary related to developer experience through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 1 other vocabulary module. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.