One of the hardest challenges for non-native English speakers — knowing when to use a, an, the, or no article at all. This exercise focuses on the patterns that come up most in IT communication.
The 4 article rules you'll practise
an HTTP / an API — use "an" before acronyms that start with a vowel sound
∅ production / ∅ localhost — no article with IT environment names
∅ JavaScript / ∅ Python — no article with language and product names
a bug → the bug — indefinite for first mention, definite for known reference
0 / 5 completed
1 / 5
A backend developer documents an API endpoint. Which sentence is correct?
"Client receives ___ HTTP response with status 201."
An HTTP — the rule: use "an" before words that start with a vowel SOUND.
The article choice is based on how the following word is pronounced, not spelled:
Acronyms said letter by letter → first letter determines the article:
An HTTP request — "H" is pronounced "aitch" (vowel sound)
An API endpoint — "A" is pronounced "ay" (vowel sound)
An SQL query — "S" is pronounced "ess" (vowel sound)
An IDE — "I" is pronounced "eye" (vowel sound)
A URL — "U" is pronounced "you" (consonant sound)
A UI/UX designer — "U" sounds like "you"
Words pronounced as words → first sound determines the article:
A YAML file — "YAML" starts with /j/ sound (consonant)
A REST API — "REST" starts with /r/ (consonant)
A JSON object — "JSON" starts with /dʒ/ "jay" (consonant)
2 / 5
A developer talks about their project architecture. Which sentence uses articles correctly?
"We split the application into ___ frontend and ___ backend."
A frontend vs. the frontend — context determines the article.
Both "a" and "the" can be correct depending on what you're referring to:
Use "a" (indefinite): when introducing the concept generically, or when it could be any frontend/backend:
"We split the app into a frontend and a backend." — describing the architecture pattern in general
"We need to hire a frontend developer." — any frontend developer
Use "the" (definite): when referring to a specific, known part of a specific system:
"The frontend is built in React." — your project's specific frontend
"The backend is deployed on AWS." — your system's backend
"I work on the frontend, she works on the backend." — the established parts of your team's application
Note: Once a part of a system has been introduced, use "the" for subsequent references. "We have a frontend. The frontend is built with Vue."
3 / 5
A CV (resume) states: "I have 5 years of experience working with ___ JavaScript and ___ React framework."
Which article usage is correct?
No article with programming language names and technology names used generically.
No article (∅):
"I work with ∅ JavaScript." — language name, used generically
"I build apps in ∅ Python." — no article
"Our system uses ∅ Docker and ∅ Kubernetes." — product names
"She's learning ∅ TypeScript."
Use "the" with a full noun phrase:
"I know the React framework." — the specific, well-known framework
"The JavaScript ecosystem is huge." — referring to the ecosystem as a concept
"The Python standard library…" — specific part of a specific language
Use "a/an" when the technology is being described generally:
"React is a JavaScript framework." — describing what React is
"We chose a relational database." — referring to a category, not a specific product
4 / 5
A QA engineer writes a bug report: "There is ___ bug in ___ production that causes ___ crash on login."
Which combination is correct?
Article usage with "production" and similar IT environment words:
"Production" (and similar environments) used without article: Words like "production", "staging", "development", "localhost" are used as proper nouns or fixed expressions in IT English — no article when used in this context:
"deployed to ∅ production" ✅
"broken in ∅ staging" ✅
"runs on ∅ localhost" ✅
"the production environment" ✅ — when you use the full noun phrase, an article is needed
"A bug" — use indefinite article: Bug is a count noun. The first mention needs "a" because it's not yet known to the reader:
"There is a bug" — first mention (any bug, not yet identified)
"The bug was caused by…" — second mention (now we know which bug)
"A crash" — use indefinite article: Same rule — first mention, count noun, use "a".
5 / 5
In a standup, a developer says: "I'm still working on ___ issue we discussed yesterday. ___ issue is in the auth module."
Which articles are correct for the first and second blank?
Definite vs. indefinite articles: first mention vs. known reference.
This is one of the most important article rules in English — and in everyday IT communication:
First mention: use "a/an" (indefinite) When something is mentioned for the first time, or is introduced as new information, use "a/an":
"I found a bug in the auth module." — first time mentioning this bug
"There's an issue in prod." — introducing unknown information
Second mention (or already known): use "the" (definite) Once the listener/reader knows what you're referring to, switch to "the":
"I found a bug. The bug is in the login handler." — second mention
"There's an issue in prod. The issue affects all EU users." — second mention
Why option C is also valid: "…working on the issue we discussed yesterday…" — if both speakers discussed this issue yesterday, it's already known context → "the" is correct for the first occurrence too.
In standup conversations: "the issue", "the PR", "the ticket" are common because everyone on the team already knows what's being referred to.