Master the natural word combinations used in developer relations and advocacy work in English. These collocations appear in community posts, conference talks, blog articles, and outreach emails.
0 / 5 completed
1 / 5
The developer advocate will ___ a workshop to help the community adopt the new SDK.
We 'run a workshop' in professional English. 'Run' is the standard verb for organising and facilitating workshops, sessions, or events. You can also 'host a workshop' or 'conduct a workshop', but 'run' is the most natural in casual and semi-formal contexts.
2 / 5
She worked hard to ___ developer trust by publishing transparent changelogs and responding to community issues.
We 'build trust' — this is a fixed collocation. 'Build' collocates with abstract things that grow over time: build trust, build rapport, build credibility. 'Create trust' is possible but less natural; 'make trust' is incorrect in English.
3 / 5
The advocacy team decided to ___ feedback from developers before finalising the API design.
We 'gather feedback' in professional English. Both 'gather' and 'collect' work, but 'gather feedback' is the dominant collocation in tech and UX contexts. 'Take feedback' is informal and less precise; 'catch feedback' is not standard.
4 / 5
He wrote a blog post to ___ awareness of the deprecation timeline among the developer community.
We 'raise awareness' — this is a fixed collocation used in communications, marketing, and advocacy. 'Spread awareness' is increasingly used informally, but 'raise awareness' is the standard professional form. 'Grow awareness' is not idiomatic.
5 / 5
The developer advocate gave a ___ talk at the conference to introduce the new platform features.
We give a 'keynote talk' or 'keynote speech'. 'Keynote' is the established term for the main, featured talk at a tech conference. 'Headline talk' is sometimes used informally, but 'keynote' is the professional standard collocation.