Build fluency in the vocabulary of a surface-level warning sign hinting at a deeper design problem.
0 / 5 completed
1 / 5
At standup, a dev mentions a function that's grown to several hundred lines, handles a dozen unrelated responsibilities, and is dreaded by everyone who has to touch it, even though it technically still works correctly. What is this surface-level warning sign called?
A code smell is a surface-level warning sign, like a several-hundred-line function juggling a dozen unrelated responsibilities, that doesn't necessarily mean the code is broken, but strongly suggests a deeper design problem is lurking underneath and making the code harder to understand, test, and safely change. Technical debt is a related but broader concept describing the accumulated cost of past shortcuts across a codebase, whereas a code smell is a specific, concrete, observable pattern. This oversized, do-everything function is one of the most classic and immediately recognizable code smells, often called a 'god function' or 'god object' when it applies to an entire class.
2 / 5
During a design review, the team splits a several-hundred-line function into a handful of smaller functions, each with one clear responsibility, specifically in response to identifying it as a code smell. Which capability does this refactor support?
This refactor supports making each smaller piece easier to read, test in isolation, and safely modify, since a function with one clear, focused responsibility is dramatically easier to reason about, write a targeted unit test for, and change without accidentally breaking an unrelated concern bundled into the same function. Claiming the split provides no benefit ignores exactly why code smells like an oversized, multi-responsibility function are flagged as problems worth fixing in the first place. This single-responsibility refactor is one of the most common and effective responses once a code smell like this has been identified.
3 / 5
In a code review, a dev notices the exact same ten-line block of logic duplicated verbatim across five different files, with no shared function or module extracting it into one place. What does this represent?
This is a duplicated-code smell, since having the same logic copy-pasted across five files means any future bug fix or behavioral change has to be found and correctly applied in all five locations, and missing even one leaves the system with inconsistent, silently diverging behavior. A load-balancing algorithm is an unrelated concept about distributing network traffic. This is exactly why duplicated logic is one of the most commonly cited code smells, and why extracting it into a single shared function or module is one of the most immediately valuable refactors a team can make.
4 / 5
An incident report shows a bug fix was applied to one copy of a duplicated validation rule but missed four other copies of the same logic scattered across the codebase, leaving inconsistent behavior between different code paths that were supposed to enforce the identical rule. What practice would prevent this?
Extracting the duplicated logic into a single shared function or module ensures a future fix only ever needs to be applied in one place, eliminating the exact risk that caused this incident, where a fix was correctly applied to one copy but missed four others. Continuing to leave the logic duplicated and relying on manually remembering every copy is precisely the fragile practice that led to the inconsistent behavior described. This single-source-of-truth extraction is the standard remedy once duplicated-code has been identified as a smell worth addressing.
5 / 5
During a PR review, a teammate asks why the team treats an oversized, multi-responsibility function as worth refactoring even though it currently passes all its tests and works correctly in production. What is the reasoning?
A code smell like an oversized, multi-responsibility function doesn't mean the code is currently broken, since it can absolutely pass every existing test and work correctly today, but it signals that future changes touching that function will be harder to reason about, riskier to get right, and slower to test in isolation, because so many unrelated concerns are bundled together in one place. Addressing it proactively, while the team still has good context on how it works, is generally far cheaper than continuing to layer new changes onto an already-tangled function and paying that cost repeatedly on every future modification. The tradeoff is the immediate time investment of refactoring something that isn't technically broken, weighed against the compounding cost of continuing to work around a known structural problem indefinitely.
What does the "Code Smell Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to code smell vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 11 other vocabulary modules. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.