8 exercises — learn how to say SQL, NGINX, GIF, JWT, IPv6, Linux, char, and Kubernetes correctly in English-speaking tech teams.
0 / 28 completed
1 / 28
How is "SQL" most commonly pronounced in English-speaking tech teams?
"sequel" — SQL was originally called SEQUEL (Structured English Query Language) before being shortened to SQL. Most English-speaking developers say "sequel". You will occasionally hear "S-Q-L" (some database administrators and formal documentation prefer this). Both are understood, but "sequel" is the dominant pronunciation in day-to-day conversation. Usage: "Let me write a sequel query", "the sequel database", "sequel server" (Microsoft SQL Server).
2 / 28
How is "NGINX" correctly pronounced?
"engine-x" — NGINX is pronounced "engine-x". This comes from the original Russian pronunciation (Nginx was created by Igor Sysoev). The logo reinforces this with the stylised N. You will almost never hear a native speaker say "N-G-I-N-X" in conversation. Usage: "The engine-x config lives in /etc/nginx/", "proxy through engine-x with SSL termination".
3 / 28
How is "GIF" most commonly pronounced?
Both are widely accepted — This is genuinely contested. Steve Wilhite, GIF's creator, insisted on "jiff" (soft g). Many developers use "gif" (hard g, like "gift"). Both are immediately understood. The creator's preference is "jiff" but the hard-g pronunciation is equally common and not wrong. You will not be corrected for either. Just stay consistent within a conversation.
4 / 28
How is "JWT" typically pronounced in conversation?
"jot" — JWT (JSON Web Token) is informally pronounced "jot" by most developers. This is the official preferred pronunciation according to the JWT specification (RFC 7519). In formal contexts you may spell it out letter by letter (J-W-T), but in daily conversation "jot" is standard. "I signed the jot with the private key", "check the jot expiry", "the jot payload is base64-encoded".
5 / 28
How is "IPv6" pronounced?
Both "I-P-version-six" and "I-P-v-six" are correct — you will hear both in conversation. "IPv6" is typically read as "I-P-v-six" in fast speech and "I-P-version-six" in formal or explanatory contexts. "Migrate to I-P-v-six addressing" and "the server doesn't support I-P-version-six yet" are both natural. Note: IPv4 follows the same pattern — "I-P-v-four" or "I-P-version-four".
6 / 28
How is "Linux" most commonly pronounced in English?
Both "LY-nux" (American style) and "LIN-ux" are widely used — Linus Torvalds himself pronounces it "LIN-us" (short I), consistent with his Finnish name Linus. However, "LY-nux" (long I) is also very common in American English. In practice you will hear both and neither is wrong. For reference, Linus's recorded pronunciation is at kernel.org. Linux distributions like "Linus-inspired Unix" make the short-I reading logical.
7 / 28
How is "char" (a single character data type) pronounced in code reviews and discussions?
Both "car" and "care" are heard in tech teams — "char" (short for character) is an interesting regional split. British and Australian developers tend to say "char" (rhymes with "bar"/"car"). American developers often say "char" rhyming with "care" or "air". In international teams, both are understood immediately from context. You will never be misunderstood regardless of pronunciation in a code review: "is this a char or a string?" is clear both ways.
8 / 28
How is "Kubernetes" correctly pronounced?
"koo-ber-NET-ees" — Kubernetes comes from the Greek κυβερνήτης (kybernetes) meaning helmsman or navigator. The official pronunciation is "koo-ber-NET-ees" (stress on the third syllable). It is commonly shortened to "k8s" (K-eight-S) in writing, pronounced "kates". In fast conversational speech you will often hear "koo-ber-netes" or "kates". Usage: "The kates cluster is running on GKE", "koo-ber-NET-ees handles container orchestration".
9 / 28
Reviewer: 'I'm seeing some issues with the API response. The JSON is malformed and the authentication token is missing. It's throwing a 401.'
Developer: 'Okay, let's debug this. Can you double-check that the request header includes the Authorization field correctly?'
This question tests understanding of the common pronunciation and usage of 'Authorization' within a code review context. Often, non-native speakers mispronounce it or use incorrect phrasing when discussing API requests. The correct answer highlights that 'Authorization' is the standard term for the HTTP header used to send authentication credentials, directly addressing the reviewer's concern. Options A and B represent common pronunciation errors; option C incorrectly interprets the context of the comment.
10 / 28
Reviewer: 'The CI build failed again. The logs show a '500' error and mention something about 'SSE' causing the issue.'
Developer: 'Let's investigate. Can you provide me with the full SSE payload from the build log?'
The acronym 'SSE' stands for Server-Sent Events. The correct pronunciation is 'Sigh-Sigh', which reflects the sound of the letters when spoken. Many non-native English speakers mispronounce it due to not being familiar with the technical term. Options A, C, and D are all incorrect phonetic interpretations that don't align with how native English speakers would naturally pronounce the acronym.
11 / 28
Reviewer: 'The build is failing intermittently. The error logs show a 'REST' endpoint returning a 503 status code.'
Developer: 'Let's check the configuration. Are you sure we're using the correct REST API version?'
This question targets a common pronunciation misunderstanding of 'REST'. While it's often pronounced with a long 'a', the most widely accepted and technically accurate pronunciation is with a short 'e' sound, mirroring its origins as an acronym. Mispronouncing can lead to confusion during technical discussions and potentially misinterpretations of API documentation or error messages. The key here is understanding that acronyms are frequently pronounced based on their initial letters.
12 / 28
During a standup update, Sarah says: 'We're seeing some performance issues with our data access layer. The queries are timing out frequently and the logs show lots of 'NoSQL' errors.' John, a more senior developer, corrects her pronunciation. What is John most likely to say?
The correct pronunciation of 'NoSQL' is often debated, but Nyoo-Ess-Kull (emphasizing the first syllable) is the most widely accepted and common usage within the tech community. The misconception behind option A is a misinterpretation of how to break down the syllables. Option B is incorrect as it overemphasizes the 'Ess' part. Option C is also incorrect, and option D reflects a misunderstanding of technical terminology.
13 / 28
During a code review of a new microservice deployment, Mark comments: 'I'm getting this weird error message - 'JSON5' – and I can't figure out why it's failing. It seems to be related to how we're handling data validation.' David, the team lead, responds to help him understand the issue. What is David most likely to say to clarify Mark's concern?
The term 'JSON5' is frequently misheard or misspelled. The correct pronunciation and common usage is JSON5 (pronounced as 'json five'), referring to a dialect of JSON that includes support for schema validation. David's response focuses on the core issue – inspecting the request payload - which is where errors are most commonly found when using JSON-based APIs, rather than simply correcting a misspelling or assuming a different meaning.
14 / 28
Reviewer: 'I'm seeing some issues with the API response. The JSON is malformed and the authentication token is missing. It's throwing a 401.'
Developer: 'Okay, let's debug this. Can you double-check that the request header includes the Authorization field correctly?'
This question tests understanding of the common pronunciation and usage of 'Authorization' within a code review context. Often, non-native speakers mispronounce it or use incorrect phrasing when discussing API requests. The correct answer highlights that 'Authorization' is the standard term for the HTTP header used to send authentication credentials, directly addressing the reviewer's concern. Options A and B represent common pronunciation errors; option C incorrectly interprets the context of the comment.
15 / 28
Reviewer: 'The CI build failed again. The logs show a '500' error and mention something about 'SSE' causing the issue.'
Developer: 'Let's investigate. Can you provide me with the full SSE payload from the build log?'
The acronym 'SSE' stands for Server-Sent Events. The correct pronunciation is 'Sigh-Sigh', which reflects the sound of the letters when spoken. Many non-native English speakers mispronounce it due to not being familiar with the technical term. Options A, C, and D are all incorrect phonetic interpretations that don't align with how native English speakers would naturally pronounce the acronym.
16 / 28
Reviewer: 'The build is failing intermittently. The error logs show a 'REST' endpoint returning a 503 status code.'
Developer: 'Let's check the configuration. Are you sure we're using the correct REST API version?'
This question targets a common pronunciation misunderstanding of 'REST'. While it's often pronounced with a long 'a', the most widely accepted and technically accurate pronunciation is with a short 'e' sound, mirroring its origins as an acronym. Mispronouncing can lead to confusion during technical discussions and potentially misinterpretations of API documentation or error messages. The key here is understanding that acronyms are frequently pronounced based on their initial letters.
17 / 28
During a standup update, Sarah says: 'We're seeing some performance issues with our data access layer. The queries are timing out frequently and the logs show lots of 'NoSQL' errors.' John, a more senior developer, corrects her pronunciation. What is John most likely to say?
The correct pronunciation of 'NoSQL' is often debated, but Nyoo-Ess-Kull (emphasizing the first syllable) is the most widely accepted and common usage within the tech community. The misconception behind option A is a misinterpretation of how to break down the syllables. Option B is incorrect as it overemphasizes the 'Ess' part. Option C is also incorrect, and option D reflects a misunderstanding of technical terminology.
18 / 28
During a code review of a new microservice deployment, Mark comments: 'I'm getting this weird error message - 'JSON5' – and I can't figure out why it's failing. It seems to be related to how we're handling data validation.' David, the team lead, responds to help him understand the issue. What is David most likely to say to clarify Mark's concern?
The term 'JSON5' is frequently misheard or misspelled. The correct pronunciation and common usage is JSON5 (pronounced as 'json five'), referring to a dialect of JSON that includes support for schema validation. David's response focuses on the core issue – inspecting the request payload - which is where errors are most commonly found when using JSON-based APIs, rather than simply correcting a misspelling or assuming a different meaning.
19 / 28
Reviewer: 'I'm seeing some issues with the API response. The JSON is malformed and the authentication token is missing. It's throwing a 401.'
Developer: 'Okay, let's debug this. Can you double-check that the request header includes the Authorization field correctly?'
This question tests understanding of the common pronunciation and usage of 'Authorization' within a code review context. Often, non-native speakers mispronounce it or use incorrect phrasing when discussing API requests. The correct answer highlights that 'Authorization' is the standard term for the HTTP header used to send authentication credentials, directly addressing the reviewer's concern. Options A and B represent common pronunciation errors; option C incorrectly interprets the context of the comment.
20 / 28
Reviewer: 'The CI build failed again. The logs show a '500' error and mention something about 'SSE' causing the issue.'
Developer: 'Let's investigate. Can you provide me with the full SSE payload from the build log?'
The acronym 'SSE' stands for Server-Sent Events. The correct pronunciation is 'Sigh-Sigh', which reflects the sound of the letters when spoken. Many non-native English speakers mispronounce it due to not being familiar with the technical term. Options A, C, and D are all incorrect phonetic interpretations that don't align with how native English speakers would naturally pronounce the acronym.
21 / 28
Reviewer: 'The build is failing intermittently. The error logs show a 'REST' endpoint returning a 503 status code.'
Developer: 'Let's check the configuration. Are you sure we're using the correct REST API version?'
This question targets a common pronunciation misunderstanding of 'REST'. While it's often pronounced with a long 'a', the most widely accepted and technically accurate pronunciation is with a short 'e' sound, mirroring its origins as an acronym. Mispronouncing can lead to confusion during technical discussions and potentially misinterpretations of API documentation or error messages. The key here is understanding that acronyms are frequently pronounced based on their initial letters.
22 / 28
During a standup update, Sarah says: 'We're seeing some performance issues with our data access layer. The queries are timing out frequently and the logs show lots of 'NoSQL' errors.' John, a more senior developer, corrects her pronunciation. What is John most likely to say?
The correct pronunciation of 'NoSQL' is often debated, but Nyoo-Ess-Kull (emphasizing the first syllable) is the most widely accepted and common usage within the tech community. The misconception behind option A is a misinterpretation of how to break down the syllables. Option B is incorrect as it overemphasizes the 'Ess' part. Option C is also incorrect, and option D reflects a misunderstanding of technical terminology.
23 / 28
During a code review of a new microservice deployment, Mark comments: 'I'm getting this weird error message - 'JSON5' – and I can't figure out why it's failing. It seems to be related to how we're handling data validation.' David, the team lead, responds to help him understand the issue. What is David most likely to say to clarify Mark's concern?
The term 'JSON5' is frequently misheard or misspelled. The correct pronunciation and common usage is JSON5 (pronounced as 'json five'), referring to a dialect of JSON that includes support for schema validation. David's response focuses on the core issue – inspecting the request payload - which is where errors are most commonly found when using JSON-based APIs, rather than simply correcting a misspelling or assuming a different meaning.
24 / 28
Reviewer: 'I'm seeing some issues with the API response. The JSON is malformed and the authentication token is missing. It's throwing a 401.'
Developer: 'Okay, let's debug this. Can you double-check that the request header includes the Authorization field correctly?'
This question tests understanding of the common pronunciation and usage of 'Authorization' within a code review context. Often, non-native speakers mispronounce it or use incorrect phrasing when discussing API requests. The correct answer highlights that 'Authorization' is the standard term for the HTTP header used to send authentication credentials, directly addressing the reviewer's concern. Options A and B represent common pronunciation errors; option C incorrectly interprets the context of the comment.
25 / 28
Reviewer: 'The CI build failed again. The logs show a '500' error and mention something about 'SSE' causing the issue.'
Developer: 'Let's investigate. Can you provide me with the full SSE payload from the build log?'
The acronym 'SSE' stands for Server-Sent Events. The correct pronunciation is 'Sigh-Sigh', which reflects the sound of the letters when spoken. Many non-native English speakers mispronounce it due to not being familiar with the technical term. Options A, C, and D are all incorrect phonetic interpretations that don't align with how native English speakers would naturally pronounce the acronym.
26 / 28
Reviewer: 'The build is failing intermittently. The error logs show a 'REST' endpoint returning a 503 status code.'
Developer: 'Let's check the configuration. Are you sure we're using the correct REST API version?'
This question targets a common pronunciation misunderstanding of 'REST'. While it's often pronounced with a long 'a', the most widely accepted and technically accurate pronunciation is with a short 'e' sound, mirroring its origins as an acronym. Mispronouncing can lead to confusion during technical discussions and potentially misinterpretations of API documentation or error messages. The key here is understanding that acronyms are frequently pronounced based on their initial letters.
27 / 28
During a standup update, Sarah says: 'We're seeing some performance issues with our data access layer. The queries are timing out frequently and the logs show lots of 'NoSQL' errors.' John, a more senior developer, corrects her pronunciation. What is John most likely to say?
The correct pronunciation of 'NoSQL' is often debated, but Nyoo-Ess-Kull (emphasizing the first syllable) is the most widely accepted and common usage within the tech community. The misconception behind option A is a misinterpretation of how to break down the syllables. Option B is incorrect as it overemphasizes the 'Ess' part. Option C is also incorrect, and option D reflects a misunderstanding of technical terminology.
28 / 28
During a code review of a new microservice deployment, Mark comments: 'I'm getting this weird error message - 'JSON5' – and I can't figure out why it's failing. It seems to be related to how we're handling data validation.' David, the team lead, responds to help him understand the issue. What is David most likely to say to clarify Mark's concern?
The term 'JSON5' is frequently misheard or misspelled. The correct pronunciation and common usage is JSON5 (pronounced as 'json five'), referring to a dialect of JSON that includes support for schema validation. David's response focuses on the core issue – inspecting the request payload - which is where errors are most commonly found when using JSON-based APIs, rather than simply correcting a misspelling or assuming a different meaning.
What will I practice in "Correct Pronunciation — IT Abbreviations Exercises"?
This is an IT Abbreviations exercise set. It walks through 28 scenario-based multiple-choice questions built around real usage of IT Abbreviations terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 28 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the IT Abbreviations vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more IT Abbreviations exercises?
See the IT Abbreviations exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — IT Abbreviations vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.