5 exercises — the same word can mean very different things depending on context. Non-native speakers often know the everyday meaning but miss the technical one — or vice versa.
Words with multiple meanings in this set
thread — string (everyday) / email replied chain / unit of concurrent execution
fork — utensil (everyday) / fork() system call / copy a repository independently
commit — promise (everyday) / save a snapshot to Git history
token — coin substitute / NLP text unit / auth credential (JWT, OAuth)
model — fashion (everyday) / 3D mesh / MVC layer / trained ML algorithm
0 / 26 completed
1 / 26
A senior engineer writes in a code review:
"This computation is CPU-heavy — move it to a worker thread so the main thread stays responsive."
What does "thread" mean in this context?
Thread (computing) — a unit of concurrent execution within a process. A process can have multiple threads running simultaneously, sharing the same memory space. Main thread in browser JavaScript: the single thread that handles UI rendering and user events — blocking it freezes the page. Worker threads (Node.js) and Web Workers (browser): separate threads for CPU-intensive work. Thread safety: code that works correctly when accessed by multiple threads without data corruption.
The same word, different contexts: • Thread (computing) = unit of execution (this exercise) • Thread (email/Slack) = a chain of replies in one conversation ("reply in thread", "start a new thread") • Thread (everyday English) = string, fibre
All three are common in a software team's daily language. Context makes the meaning clear.
2 / 26
A team discusses an open-source project in Slack:
"The upstream project hasn't responded to the security PR in 3 months. We should fork it and maintain our own patched version."
What does "fork" mean here?
Fork (Git / open-source) — creating a personal or organizational copy of a repository that becomes independent from the original. You can make changes to your fork without affecting the original ("upstream") project. Common uses: contributing to open-source (you fork → make changes → open a pull request back to the original), or maintaining your own divergent version when upstream is inactive or doesn't meet your needs.
The same word, different contexts: • Fork (Git/GitHub) = copy a repository independently (this exercise) • Fork (Unix/Linux) = fork() system call that creates a child process by cloning the parent process — used in systems programming • Fork (project) = a project that started from another codebase and evolved independently (LibreOffice is a fork of OpenOffice) • Fork (everyday English) = the utensil; also a road junction
In team conversations: "fork the repo" = always the Git meaning.
3 / 26
In a daily standup:
"I'll commit the fixes tonight and push the branch — should be ready for review tomorrow."
What does "commit" mean here?
Commit (Git) — a snapshot of changes saved to the repository's history. Each commit has: a unique hash ID, an author, a timestamp, a commit message, and a diff. git commit -m "fix: resolve null check in payment handler" creates a new commit. Commits are the fundamental unit of change in Git — you review them in PRs, revert them if something goes wrong, cherry-pick them onto other branches, and squash them to clean up history.
The same word, different contexts: • Commit (Git) = save a snapshot of changes (this exercise — by far the most common use in a dev team) • Commit (general English) = dedicate yourself, make a promise ("are you committed to this project?") • Commit (databases) = confirm a transaction permanently (in the ACID sense: atomicity, consistency, isolation, durability)
In standup/Slack: "commit" almost always means the Git operation.
4 / 26
A frontend developer says:
"The app stores a refresh token in localStorage and uses it to get new access tokens without requiring the user to log in again."
What does "token" mean in this context?
Token (authentication) — a credential string that proves identity or grants access to resources, without requiring a password on every request. Access token: short-lived (minutes to hours), used on every API request in the Authorization header. Refresh token: long-lived (days to weeks), stored securely — used only to obtain a new access token when the old one expires. JWT (JSON Web Token): a common token format — contains encoded claims (user ID, roles, expiry) signed with a secret key.
The same word, different contexts: • Token (auth/API) = credential string — JWT, OAuth access token, API key-style token (this exercise) • Token (NLP/AI) = a unit of text that a language model processes; "this prompt uses 1,200 tokens" — GPT charges by token, which roughly = ¾ of a word • Token (blockchain) = a digital asset on a blockchain (ERC-20 token, NFT) • Token (everyday English) = a physical coin substitute
In an auth discussion: always the credential meaning.
5 / 26
A data scientist presents results:
"We trained three models on the dataset — a random forest, a gradient boosting model, and a logistic regression baseline. The random forest outperformed the others with 94% accuracy."
What does "model" mean here?
Model (machine learning / AI) — a trained algorithm that has learned patterns from data and can make predictions, classifications, or generate output for new inputs. Training a model = fitting its parameters to minimise error on training data. Examples: decision tree, neural network, linear regression, transformer (the architecture behind GPT). Key vocabulary: train a model, evaluate a model, deploy a model, fine-tune a model, model accuracy/precision/recall, baseline model (the simplest model used for comparison).
The same word, different contexts: • Model (ML/AI) = trained algorithm (this exercise — extremely common in modern tech teams) • Model (MVC architecture) = the data / business logic layer in the Model-View-Controller pattern • Model (3D graphics) = a mesh geometry object (.obj, .gltf files) • Model (data modelling) = the schema/structure of your data (ER model, domain model) • Model (everyday English) = a person who wears clothes; also a miniature representation ("model airplane")
In a data science context: always the ML training meaning.
6 / 26
During a design review for a new microservice API, a junior developer asks: "Can we use a token to authenticate requests from the mobile app? It seems simpler than OAuth."
Tokens are primarily used for session management or simple authentication. However, in a modern API design, relying solely on tokens for authentication exposes the system to significant security risks like replay attacks and lack of granular access control. OAuth provides a much more robust framework with delegated authorization and user consent – ensuring proper authorization is granted before any data access.
7 / 26
A backend engineer is debugging a slow API endpoint. After profiling, they discover that the database query is performing a full table scan. They discuss the problem with another engineer and suggest adding an index to the relevant column. The other engineer responds: 'That's a good idea – we should definitely 'commit' that change to the codebase.' What does 'commit' mean in this context?
In software development, 'commit' refers to permanently recording changes made to a version control system (like Git). This action saves the new index definition so it can be tracked and deployed along with other code updates. The misconception is that 'commit' relates to temporary actions or physical movement; it's about saving the change as part of the codebase.
8 / 26
A team is discussing a new feature for their e-commerce platform. One developer suggests using a 'token' to securely store user authentication information. Another developer asks, 'But what *is* a token in this context? Is it like an ID number or something else entirely?'
In this scenario, 'token' refers to an authentication mechanism—specifically, an access token. These tokens are commonly used in modern web applications and APIs to grant a user limited access to resources without requiring them to repeatedly enter their credentials. The key difference is that it's not a cryptographic key or a physical device; it represents authorized access.
9 / 26
A senior developer is reviewing a new feature implementation for a payment processing service. The code includes a section where user authentication details are stored as a 'token' within the session data. A junior developer asks: "I'm not entirely clear on what this 'token' actually *is*. Is it some kind of temporary key, or does it represent a specific user account?"
In this context, a 'token' is a short-lived, cryptographically signed credential that represents an authenticated session. Unlike a user ID, it doesn't directly identify a specific account but rather proves the user has been successfully verified and authorized to access the service without revealing their actual credentials (like a password or credit card details). This protects against session hijacking and ensures secure communication.
10 / 26
During a design review for a new microservice API, a junior developer asks: "Can we use a token to authenticate requests from the mobile app? It seems simpler than OAuth."
Tokens are primarily used for session management or simple authentication. However, in a modern API design, relying solely on tokens for authentication exposes the system to significant security risks like replay attacks and lack of granular access control. OAuth provides a much more robust framework with delegated authorization and user consent – ensuring proper authorization is granted before any data access.
11 / 26
A backend engineer is debugging a slow API endpoint. After profiling, they discover that the database query is performing a full table scan. They discuss the problem with another engineer and suggest adding an index to the relevant column. The other engineer responds: 'That's a good idea – we should definitely 'commit' that change to the codebase.' What does 'commit' mean in this context?
In software development, 'commit' refers to permanently recording changes made to a version control system (like Git). This action saves the new index definition so it can be tracked and deployed along with other code updates. The misconception is that 'commit' relates to temporary actions or physical movement; it's about saving the change as part of the codebase.
12 / 26
A team is discussing a new feature for their e-commerce platform. One developer suggests using a 'token' to securely store user authentication information. Another developer asks, 'But what *is* a token in this context? Is it like an ID number or something else entirely?'
In this scenario, 'token' refers to an authentication mechanism—specifically, an access token. These tokens are commonly used in modern web applications and APIs to grant a user limited access to resources without requiring them to repeatedly enter their credentials. The key difference is that it's not a cryptographic key or a physical device; it represents authorized access.
13 / 26
A senior developer is reviewing a new feature implementation for a payment processing service. The code includes a section where user authentication details are stored as a 'token' within the session data. A junior developer asks: "I'm not entirely clear on what this 'token' actually *is*. Is it some kind of temporary key, or does it represent a specific user account?"
In this context, a 'token' is a short-lived, cryptographically signed credential that represents an authenticated session. Unlike a user ID, it doesn't directly identify a specific account but rather proves the user has been successfully verified and authorized to access the service without revealing their actual credentials (like a password or credit card details). This protects against session hijacking and ensures secure communication.
14 / 26
During a design review for a new microservice API, a junior developer asks: "Can we use a token to authenticate requests from the mobile app? It seems simpler than OAuth."
Tokens are primarily used for session management or simple authentication. However, in a modern API design, relying solely on tokens for authentication exposes the system to significant security risks like replay attacks and lack of granular access control. OAuth provides a much more robust framework with delegated authorization and user consent – ensuring proper authorization is granted before any data access.
15 / 26
A backend engineer is debugging a slow API endpoint. After profiling, they discover that the database query is performing a full table scan. They discuss the problem with another engineer and suggest adding an index to the relevant column. The other engineer responds: 'That's a good idea – we should definitely 'commit' that change to the codebase.' What does 'commit' mean in this context?
In software development, 'commit' refers to permanently recording changes made to a version control system (like Git). This action saves the new index definition so it can be tracked and deployed along with other code updates. The misconception is that 'commit' relates to temporary actions or physical movement; it's about saving the change as part of the codebase.
16 / 26
A team is discussing a new feature for their e-commerce platform. One developer suggests using a 'token' to securely store user authentication information. Another developer asks, 'But what *is* a token in this context? Is it like an ID number or something else entirely?'
In this scenario, 'token' refers to an authentication mechanism—specifically, an access token. These tokens are commonly used in modern web applications and APIs to grant a user limited access to resources without requiring them to repeatedly enter their credentials. The key difference is that it's not a cryptographic key or a physical device; it represents authorized access.
17 / 26
A senior developer is reviewing a new feature implementation for a payment processing service. The code includes a section where user authentication details are stored as a 'token' within the session data. A junior developer asks: "I'm not entirely clear on what this 'token' actually *is*. Is it some kind of temporary key, or does it represent a specific user account?"
In this context, a 'token' is a short-lived, cryptographically signed credential that represents an authenticated session. Unlike a user ID, it doesn't directly identify a specific account but rather proves the user has been successfully verified and authorized to access the service without revealing their actual credentials (like a password or credit card details). This protects against session hijacking and ensures secure communication.
18 / 26
During a design review for a new microservice API, a junior developer asks: "Can we use a token to authenticate requests from the mobile app? It seems simpler than OAuth."
Tokens are primarily used for session management or simple authentication. However, in a modern API design, relying solely on tokens for authentication exposes the system to significant security risks like replay attacks and lack of granular access control. OAuth provides a much more robust framework with delegated authorization and user consent – ensuring proper authorization is granted before any data access.
19 / 26
A backend engineer is debugging a slow API endpoint. After profiling, they discover that the database query is performing a full table scan. They discuss the problem with another engineer and suggest adding an index to the relevant column. The other engineer responds: 'That's a good idea – we should definitely 'commit' that change to the codebase.' What does 'commit' mean in this context?
In software development, 'commit' refers to permanently recording changes made to a version control system (like Git). This action saves the new index definition so it can be tracked and deployed along with other code updates. The misconception is that 'commit' relates to temporary actions or physical movement; it's about saving the change as part of the codebase.
20 / 26
A team is discussing a new feature for their e-commerce platform. One developer suggests using a 'token' to securely store user authentication information. Another developer asks, 'But what *is* a token in this context? Is it like an ID number or something else entirely?'
In this scenario, 'token' refers to an authentication mechanism—specifically, an access token. These tokens are commonly used in modern web applications and APIs to grant a user limited access to resources without requiring them to repeatedly enter their credentials. The key difference is that it's not a cryptographic key or a physical device; it represents authorized access.
21 / 26
A senior developer is reviewing a new feature implementation for a payment processing service. The code includes a section where user authentication details are stored as a 'token' within the session data. A junior developer asks: "I'm not entirely clear on what this 'token' actually *is*. Is it some kind of temporary key, or does it represent a specific user account?"
In this context, a 'token' is a short-lived, cryptographically signed credential that represents an authenticated session. Unlike a user ID, it doesn't directly identify a specific account but rather proves the user has been successfully verified and authorized to access the service without revealing their actual credentials (like a password or credit card details). This protects against session hijacking and ensures secure communication.
22 / 26
During a code review of a new microservice, Sarah comments: 'This endpoint uses a `token` for authorization. It seems straightforward, but are we sure it's the most secure approach against potential replay attacks?'. What does Sarah likely mean by 'token' in this context?
Sarah is referring to an authentication token – specifically, a JWT (JSON Web Token) which is a common method for securing APIs. Replay attacks occur when a stolen token is reused, so she's questioning whether the simple string represents sufficient protection against this vulnerability. Options B and D are incorrect as they relate to database structures or HTTP status codes.
23 / 26
Mark is writing a commit message for a change that introduces a new 'fork' in the codebase. He wants to explain the purpose concisely. Which of the following best describes what he should include?
In Git terminology, a 'fork' refers to branching off from an existing codebase to create an independent development line. Mark needs to explain the *reason* for this branch—what problem it solves or what new functionality it introduces. Options A and C are irrelevant for commit messages, and option D is simply a metric.
24 / 26
Elena sends the following Slack message: 'Just deployed the new API endpoint. The response contains a `token` to access user data. It's crucial we ensure this token is securely transmitted and validated.' What is Elena primarily concerned about?
Elena is highlighting the importance of secure transmission and validation of the authentication token – a common vulnerability. The token's integrity and confidentiality are key to preventing unauthorized access to user data. Options A, B, and D relate to different aspects of API operation but not specifically security.
25 / 26
During a standup meeting, David says: 'I'm working on implementing a `model` for the new user profile data. It's going to allow us to efficiently store and retrieve information about each user'. What does David likely mean by 'model' in this context?
In software development, a 'model' represents a conceptual design or blueprint – in this case, a structured representation of the user profile data. This definition outlines fields and relationships within that data. Options A, C, and D are incorrect interpretations.
26 / 26
A developer is reviewing a pull request and sees the following line of code: 'commit(message, token)'. What action does this command likely represent?
The `commit(message, token)` command is likely used to send a request to an API endpoint (e.g., a webhook) with a specific message and authentication token. This allows for automated actions or notifications based on changes in the codebase – often used in CI/CD pipelines. Options A, C, and D are unrelated.
What does the "IT Words With Multiple Meanings — Thread, Fork, Commit, Token, Model" exercise cover?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.
How many questions are in "IT Words With Multiple Meanings — Thread, Fork, Commit, Token, Model"?
This exercise has 26 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more False Friends & Tricky Words exercises?
Browse the full False Friends & Tricky Words hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.