A tech lead writes in a post-mortem: "The bus factor on this service is 1 — only one engineer understands the deployment process." What does a bus factor of 1 indicate?
Bus factor (also "truck factor" or "lottery number") is the minimum number of team members who could become unavailable — hit by a bus — before a project comes to a complete halt. A bus factor of 1 is a critical risk: if that one person leaves, gets sick, or is otherwise unavailable, the team is stuck. A high bus factor (e.g., 5) means knowledge is well distributed. Improving bus factor: pair programming, documentation sprints, code reviews, and mentoring. Some teams use "lottery factor" as a more optimistic version — what if someone wins the lottery and quits tomorrow? Either way, it's a genuine engineering risk metric.
2 / 15
In a job listing, a startup writes: "We're a small team — you'll need to wear many hats: backend development, DevOps, and occasionally jumping into customer support." What does wearing many hats mean?
Wearing many hats comes from the idea of literally putting on different hats to assume different roles — a cowboy hat for one job, a hard hat for another. In a startup or small team context, it means one person is expected to perform multiple distinct roles. It can be attractive (you learn a lot) or exhausting (you're spread thin). When reading job descriptions: "wear many hats" almost always means "we're understaffed — you'll do more than one person's job." Related terms: "generalist" (vs. specialist), "full-stack" (technical version — handles both front and back), "T-shaped" (deep in one area, broad across others).
3 / 15
After a team restructuring, the engineering manager says: "We're trying to break down the knowledge silos — the frontend team had no idea how the API worked, and the backend team never spoke to design." What are knowledge silos?
Knowledge silos borrow from agricultural silos — tall grain storage containers that stand separately and don't mix. In organizations, silos are departments or individuals that hold expertise without sharing it with the rest of the team. This is a serious organizational risk: decisions are made without the full picture, on-boarding is slow (because one person holds all the context), and the bus factor stays low. Breaking down silos means: shared documentation, cross-functional teams, regular demos, and architectural decision records (ADRs) that everyone can read. "Silo mentality" (a related phrase) refers to a team or person who actively resists sharing information with others.
4 / 15
A developer asks in a Slack channel: "What does it actually mean when job posts say they're looking for a 10x developer?" What is typically meant by a 10x developer?
10x developer (or "10x engineer") is a claim that a single exceptional engineer can produce 10 times the output of an average engineer. The origin is a disputed interpretation of research studies from the 1960s–80s comparing programmer productivity. In practice, the term is highly controversial: critics argue it's used to justify hero culture, overwork, and poor team dynamics. Supporters say genuinely exceptional engineers can indeed multiply the productivity of a team — but through mentoring, system design, and unblocking others, not through raw code output. If a job posting emphasizes "10x talent", it may signal they value individual stars over team culture. Red flag or green flag depending on your values.
5 / 15
In a performance review, a manager describes an employee: "She's a T-shaped engineer — deep expertise in distributed systems, but comfortable across the full stack and able to contribute to frontend work when needed." What is a T-shaped engineer?
T-shaped is a career and skills metaphor: the vertical stroke of the "T" represents deep expertise in one domain (e.g., distributed systems, machine learning, frontend performance); the horizontal stroke represents shallower but functional knowledge across many areas (DevOps, frontend, testing, product, etc.). It's widely regarded as the ideal engineering profile for cross-functional teams — you can go deep when needed but can also contribute meaningfully across the project. Contrast with: "I-shaped" (deep in one area, unable to help elsewhere — risky for team flexibility) and "π-shaped" (deep in two domains — highly valuable). "T-shaped" is used in hiring, career conversations, and team-building discussions.
6 / 15
Sarah from the QA team sends a message to David in Slack: "Hey David, just flagging that the integration tests are failing again. It seems like the new microservice is intermittently returning 502 errors. I've tried restarting it, but no luck.". What does 'intermittently' likely imply in this context?
'Intermittently' describes something that happens at irregular intervals. In this case, the 502 errors aren't constant; they appear sporadically. A common misconception is to assume it means 'always', but intermittent implies a lack of predictability in the failure pattern. This highlights the need for more robust monitoring and debugging.
7 / 15
Mark writes a PR description: "Implemented the user authentication flow using OAuth 2.0. Added logging to track API calls and user sessions. This ensures compliance with GDPR requirements regarding data privacy.". What is Mark primarily communicating about when he mentions 'GDPR compliance'?
GDPR (General Data Protection Regulation) is a European Union law focused on protecting the personal data of individuals. Mark's statement indicates that the authentication flow and logging mechanisms are designed to meet GDPR's requirements for handling user data – specifically, ensuring privacy and security. This is about legal compliance, not just technical best practices.
8 / 15
Emily, a senior engineer, asks her junior colleague, Ben, during a standup: "Can you give me an update on the performance of the new caching layer? We're seeing latency spikes under high load.". What is Emily likely asking Ben to investigate?
Latency spikes refer to sudden increases in the time it takes for a system to respond. Emily's question directly asks about performance—specifically response times—which are a key indicator of whether the caching layer is functioning correctly under stress. This isn't about bugs or configuration issues, but rather the *effect* of those problems.
9 / 15
Liam receives an API response from a third-party service: `{"status": "error", "code": 403, "message": "Forbidden - Insufficient permissions."}`. What does this response suggest?
A 403 Forbidden HTTP status code indicates that the client (Liam's application) does not have permission to access the resource. This isn't a server error or account issue; it's a direct consequence of lacking the correct authentication or authorization credentials for the API request. Understanding these codes is crucial for debugging and handling failures gracefully.
10 / 15
Chloe's manager provides feedback: "You're a valuable asset to the team – you consistently deliver high-quality code, but sometimes you get stuck in technical details and don't consider the broader implications of your work.". What does this feedback suggest about Chloe's current skillset?
The feedback highlights a disconnect between Chloe's technical execution (high-quality code) and the strategic understanding of her work. While important, simply writing good code isn't enough; she needs to consider the 'bigger picture'. This suggests a need for more holistic thinking and communication skills to ensure her contributions align with team goals.
11 / 15
Sarah from the QA team sends a message to David in Slack: "Hey David, just flagging that the integration tests are failing again. It seems like the new microservice is intermittently returning 502 errors. I've tried restarting it, but no luck.". What does 'intermittently' likely imply in this context?
'Intermittently' describes something that happens at irregular intervals. In this case, the 502 errors aren't constant; they appear sporadically. A common misconception is to assume it means 'always', but intermittent implies a lack of predictability in the failure pattern. This highlights the need for more robust monitoring and debugging.
12 / 15
Mark writes a PR description: "Implemented the user authentication flow using OAuth 2.0. Added logging to track API calls and user sessions. This ensures compliance with GDPR requirements regarding data privacy.". What is Mark primarily communicating about when he mentions 'GDPR compliance'?
GDPR (General Data Protection Regulation) is a European Union law focused on protecting the personal data of individuals. Mark's statement indicates that the authentication flow and logging mechanisms are designed to meet GDPR's requirements for handling user data – specifically, ensuring privacy and security. This is about legal compliance, not just technical best practices.
13 / 15
Emily, a senior engineer, asks her junior colleague, Ben, during a standup: "Can you give me an update on the performance of the new caching layer? We're seeing latency spikes under high load.". What is Emily likely asking Ben to investigate?
Latency spikes refer to sudden increases in the time it takes for a system to respond. Emily's question directly asks about performance—specifically response times—which are a key indicator of whether the caching layer is functioning correctly under stress. This isn't about bugs or configuration issues, but rather the *effect* of those problems.
14 / 15
Liam receives an API response from a third-party service: `{"status": "error", "code": 403, "message": "Forbidden - Insufficient permissions."}`. What does this response suggest?
A 403 Forbidden HTTP status code indicates that the client (Liam's application) does not have permission to access the resource. This isn't a server error or account issue; it's a direct consequence of lacking the correct authentication or authorization credentials for the API request. Understanding these codes is crucial for debugging and handling failures gracefully.
15 / 15
Chloe's manager provides feedback: "You're a valuable asset to the team – you consistently deliver high-quality code, but sometimes you get stuck in technical details and don't consider the broader implications of your work.". What does this feedback suggest about Chloe's current skillset?
The feedback highlights a disconnect between Chloe's technical execution (high-quality code) and the strategic understanding of her work. While important, simply writing good code isn't enough; she needs to consider the 'bigger picture'. This suggests a need for more holistic thinking and communication skills to ensure her contributions align with team goals.
What will I practise in "Team & People Idioms — IT English Exercises"?How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the idiom's meaning and the tone it carries — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Idioms & Expressions exercises?
Browse the full Idioms & Expressions hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain idioms and their context in prose; this exercise tests and reinforces that recognition through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.