Improving the developer experience starts with the right vocabulary. These exercises cover the collocations DevEx teams and platform engineers use when collecting, prioritising, and acting on developer feedback.
0 / 5 completed
1 / 5
The DevEx team ran a survey to ___ from all engineering squads about the CI pipeline.
Collect feedback is the standard collocation for systematically soliciting opinions through surveys or interviews. 'Gather' is equally common and more informal; 'get' is conversational; 'obtain' is too formal for a feedback exercise.
2 / 5
The platform team prioritised the build-time regression to ___ that developers had raised repeatedly.
Address pain points is the standard collocation in product and DevEx work for responding to identified problems. 'Address' implies investigation, prioritisation, and resolution. 'Fix' and 'solve' focus only on resolution; 'remove' implies elimination, which is not always possible.
3 / 5
The internal developer platform initiative was launched to ___ and cut build times in half.
Improve tooling is the standard DevEx collocation for enhancing developer tools and workflows. 'Improve' is the general, professional-grade verb for this context. 'Upgrade' implies a version update; 'fix' implies defects only; 'better' is not used as a verb in professional English.
4 / 5
The goal of the new scaffolding tool is to ___ for engineers creating new microservices.
Reduce friction is the canonical DevEx and product collocation for decreasing the effort or obstacles in a workflow. 'Reduce' is the standard verb in developer experience literature. 'Lower' and 'cut' are alternatives; 'remove' implies complete elimination, which is rarely achievable.
5 / 5
The product manager used the survey results to ___ for the developer platform team.
Prioritise improvements is the standard product management collocation for ordering work by value or impact. 'Prioritise' is the professional term used in roadmap and backlog management. 'Rank' and 'order' are more mechanical; 'sort' is informal.