Practice the key verb+noun collocations used when improving developer experience, reducing friction, and measuring satisfaction in English.
0 / 5 completed
1 / 5
Fill in: 'Our platform team's mission is to ___ the developer experience across all product squads.'
We 'improve developer experience' — 'improve' is the standard DX collocation used in job descriptions, OKRs, and engineering blogs. 'Enhance' is slightly more formal; 'better' as a verb sounds informal; 'boost' is too casual and implies a quick fix.
2 / 5
Fill in: 'We simplified the local setup to ___ the friction new engineers face on day one.'
We 'reduce friction' — 'reduce friction' is the DX standard collocation for making processes less cumbersome. 'Remove friction' implies complete elimination; 'cut friction' is informal; 'eliminate friction' is the ambitious goal, while 'reduce' is the realistic improvement.
3 / 5
Fill in: 'We moved to a monorepo to ___ the build process and avoid duplicated tooling config.'
We 'streamline the build' — 'streamline' specifically implies making a process more efficient and eliminating unnecessary steps. 'Simplify' focuses on reducing complexity; 'speed up' focuses on performance; 'improve' is too generic.
4 / 5
Fill in: 'Faster CI pipelines help ___ feedback loops so engineers can iterate more quickly.'
We 'shorten feedback loops' — 'shorten' is the precise DX collocation for reducing the time between a code change and seeing its result. 'Reduce feedback loops' is less idiomatic; 'tighten' is informal; 'accelerate' is used for processes, not loops.
5 / 5
Fill in: 'We ran a quarterly survey to ___ developer satisfaction and identify areas for improvement.'
We 'measure developer satisfaction' — 'measure' is the data-driven DX collocation for quantifying how satisfied engineers are with their tools and processes. 'Track' implies ongoing monitoring over time; 'assess' is evaluative; 'gauge' is informal and less precise.