5 exercises on pair programming phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
You are the navigator and want to take over as driver for a moment. How do you ask politely?
Option C is the most professional request. 'Would you mind if I drive for a bit?' softens the ask with a question form, 'for a bit' frames it as temporary rather than a takeover, and 'I want to try something' signals a concrete purpose without being vague. 'Give me the keyboard' (A) is abrupt and sounds like a command. 'Can I have a go?' (B) is too casual and slightly childlike. 'Let me do it instead' (D) sounds dismissive of what your partner is doing. In pair programming, transitions between driver and navigator work best when they're framed as invitations with a stated reason.
2 / 10
As navigator, you can see a cleaner approach but you don't want to take over. Which phrase best suggests your idea?
Option B uses the classic navigator move: a 'what if' question that offers a concrete suggestion (extract to helper function) and gives a reason tied to a shared goal (cleaner test). It invites rather than instructs. 'That's not right' (A) is a criticism without a direction, which stalls the session. 'I would do it differently' (C) expresses preference without explaining what or why. 'You should try another way' (D) is prescriptive without being helpful. The best navigator phrases are questions with a reason: 'What if we X? It would Y.' The driver can then choose to take the suggestion or explain why they prefer the current path.
3 / 10
You spot a potential null pointer exception in the code your pair is writing. How do you raise it diplomatically?
Option D is specific and precise. It flags the concern ('potential issue'), names the exact condition that triggers it ('if the list is empty'), and identifies the exact failure ('null pointer exception') — all without implying your pair made a careless mistake. 'That's a bug' (A) is blunt and slightly accusatory. 'This won't work' (B) is a strong assertion that invites defensiveness. 'I'm not sure about that' (C) raises doubt without giving any information. In pair programming, specific bug observations create useful conversations; vague criticism creates friction. Always name the condition and the consequence.
4 / 10
Your pair is writing code in a way you don't fully follow. How do you ask them to walk you through it?
Option A is the most collaborative phrasing. It opens with a request ('can you talk me through'), explains why ('I want to make sure I follow the approach'), and frames the question as seeking understanding, not challenging the decision. 'Why are you doing it that way?' (B) is grammatically fine but can sound like a challenge depending on tone — in text or at the keyboard, it often lands as skeptical. 'I don't understand what you're doing' (C) is honest but passive; it doesn't request any specific action. 'Explain this to me' (D) is blunt and slightly commanding. The best learning requests in pairing combine the ask with a stated purpose.
5 / 10
You want to suggest writing the failing test before implementing the feature. Which phrase introduces this most effectively?
Option C is specific and persuasive. It proposes a concrete action ('write the failing test first'), times it precisely ('before we implement this'), and gives a clear benefit ('it'll make the expected behaviour concrete'). 'We should do TDD' (A) is an abstract principle, not an actionable suggestion for this moment. 'Let's write tests before code' (B) is closer but still abstract — which test, for what? 'I think testing is important' (D) is a general value statement with no action attached. Effective pair programming proposals are concrete: they name the next action, when to do it, and why it helps this specific piece of work.
6 / 10
During a code review of Sarah's PR for the user authentication module, you notice she's using a synchronous call to an external API. You want to gently suggest asynchronous handling to avoid blocking the main thread. Which phrase would be most appropriate to use in your comment? // Consider using async/await here
The key here is to frame your suggestion constructively. Option 1 directly proposes a solution without being critical. Options 2 and 3 invite discussion and understanding of Sarah's choice, while option 4 dismisses the concern entirely – which isn't helpful in a collaborative review. It's important to offer guidance, not simply point out a potential issue.
7 / 10
You're in a Slack channel discussing the upcoming sprint with David and Maria. David is struggling to understand the new database schema. You want to offer support without making him feel inadequate. Which of the following messages would best demonstrate collaboration? /msg @david 'Just let me know if you'd like a quick walkthrough of the schema!'
This scenario emphasizes supportive communication. Option 1 is dismissive and potentially demoralizing. Option 2 offers direct assistance, but could be perceived as overly directive. Option 3 provides platitudes that don't address the specific issue, while option 1 proactively offers help in a way that respects David's learning process – signaling willingness to assist without judgment.
8 / 10
During a standup update, Ben mentions he's working on integrating the new payment gateway. You notice he hasn't yet addressed error handling for declined payments. How can you politely prompt him to consider this during the next iteration? 'Regarding the payment integration, have you thought about how we'll handle declined transactions?'
The goal here is to gently steer Ben toward a critical consideration. Option 1 is irresponsible and could lead to serious problems down the line. Option 3 directly addresses the issue and invites discussion, while option 4 is too vague and doesn't provide any direction. Option 2 acknowledges the priority but introduces the necessary element without being overly forceful.
9 / 10
You are reviewing a PR submitted by Liam that implements a new feature for calculating shipping costs. The code uses a complex formula involving several variables and nested calculations. You want to understand his approach better before offering feedback on its correctness. Which phrase would be most effective? 'Could you walk me through the logic behind this shipping cost calculation?'
This question focuses on understanding Liam's thought process. Option 1 is simply accepting the code without investigation. Option 3 directly requests clarification, prompting a detailed explanation. Option 4, while understandable, might be perceived as condescending. Asking for a walkthrough ensures you both align on the approach and identify potential issues early.
10 / 10
You're working with Chloe on a new API endpoint. She's implemented the core logic but hasn't yet written any tests for it. You believe writing the test before implementing the feature would improve code quality. Which phrase best introduces this suggestion? 'Perhaps we should write a test for this endpoint before fully implementing it?'
This scenario highlights a proactive approach to development. Option 1 politely suggests an alternative workflow without directly criticizing Chloe's current method. Options 2 and 3 explicitly advocate for testing, which could be perceived as pushing a specific practice. Option 4 dismisses the importance of testing entirely – a crucial point to address in collaborative development.
What will I practise in "Pair Programming: Collaboration & Navigation Phrases"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.