Conditionals in Debugging and Technical Documentation
5 exercises — practise all four conditionals in technical contexts: zero for system truths, first for probable fixes, second for hypotheticals, and third for post-mortem analysis.
Conditionals in debugging
Zero (if + present, + present): system truths — "If X fails, Y crashes"
First (if + present, + will): probable fix — "If you restart it, it will recover"
Second (if + past, + would): hypothetical now — "If we had better tests, this wouldn't happen"
Third (if + past perfect, + would have): past regret — "If we had caught it earlier, we would have avoided the outage"
0 / 6 completed
1 / 6
A debugging guide states: "If the health check endpoint returns 503, ___ the upstream service is down." Which form correctly completes a zero conditional (general truth)?
It means is correct. The zero conditional (if + present simple, + present simple) expresses general truths, laws, and always-true cause-and-effect relationships. In debugging documentation, zero conditionals describe deterministic system behaviour: "If the connection pool is exhausted, new requests fail." · "If a null pointer is dereferenced, the process crashes." · "If the cache miss rate exceeds 90%, latency spikes." The defining feature: the result always happens when the condition is true — no uncertainty. Zero conditional = If + present, + present. Contrast with first conditional (if + present, + will) which is for probable future events, not universal truths.
2 / 6
An on-call engineer says: "If you restart the service, the memory leak ___ clear — I've seen this fix it before." Which form expresses a likely/probable result?
Will clear is correct. The first conditional (if + present simple, + will + infinitive) is used for probable or likely future outcomes — things that are expected to happen if the condition is met. In debugging and on-call communication: "If you roll back the deployment, the error rate will drop." · "If we increase the connection pool size, requests will stop timing out." · "If the log shows OOM, restarting will clear the heap." First conditional = probable, realistic outcome. The phrase "I've seen this fix it before" reinforces that this is an expected, likely result — not hypothetical. Contrast: would (second conditional) = hypothetical or unlikely; clears (zero) = always true.
3 / 6
A senior engineer reviews a fix and says: "If we had better test coverage, this regression ___ into production." Which form expresses a hypothetical present/future scenario (the opposite of reality)?
Wouldn't slip is correct. The second conditional (if + past simple, + would + infinitive) expresses hypothetical present/future situations contrary to current reality. Here, the engineer implies: we do NOT have good test coverage (reality), so this regression DID slip through. The second conditional imagines the alternative: "If we had [better coverage — we don't], it wouldn't slip [into production]." Tech examples: "If we had more staging environments, deployment confidence would improve." · "If the service used circuit breakers, it wouldn't cascade fail." · "If we had proper logging, we would have caught this earlier." Contrast with option A (wouldn't have slipped) — that's third conditional, referring to a past hypothetical.
4 / 6
A post-mortem document reads: "If the alerting threshold ___ been set correctly, the on-call team ___ have responded 40 minutes earlier." Which pair completes the third conditional correctly?
Had / would have is correct. The third conditional (if + past perfect, + would have + past participle) describes hypothetical situations in the past — things that didn't happen. In post-mortems: "If the threshold had been set correctly, the team would have responded earlier." = In reality, the threshold was wrong, and the team didn't respond in time. This is the most common conditional in incident post-mortems and retrospectives: "If we had had a rollback plan, recovery would have taken minutes, not hours." · "If the test had covered that edge case, the bug wouldn't have reached production." Third conditional = past regret / counterfactual. Structure: If + had + past participle, + would have + past participle.
5 / 6
A runbook instruction reads: "If the pod keeps crashing, check the OOM killer logs; if those ___ clean, examine the liveness probe configuration." Which form is correct in a zero-conditional chain of diagnostic steps?
Are is correct. In a diagnostic runbook or troubleshooting guide, chained if-then steps describing system states use the zero conditional (if + present, + present/imperative). The entire chain operates in the "always-true" domain of diagnostic logic: "If the logs are clean [= this is a consistent state], examine the liveness probe." Full runbook pattern: "If A occurs → check B. If B shows X → do C. If C fails → escalate." These are not future probabilities (no will) and not hypotheticals (no would). They are systematic diagnostic truths. Zero conditional chains are the backbone of runbooks, SOPs, and debugging guides. The imperative in the second clause (examine, check, restart) is also standard and fully correct in zero-conditional instructions.
6 / 6
A developer is investigating a slow API response. The documentation states: 'If the database connection timeout exceeds 5 seconds, immediately escalate to Tier 2 support.' Which conditional form best completes this statement?
This scenario uses a zero conditional to express a general truth: when a database connection timeout occurs, escalation is necessary. The options test understanding of zero conditionals – a direct cause and effect without 'if' or 'then'. Options B and C misinterpret the context of a technical problem.
What will I practise in "Conditionals in Debugging and Technical Documentation | Coders Lingo"?
Practise zero, first, second, and third conditionals in debugging runbooks, post-mortems, and on-call communication. 5 grammar exercises.
How many exercises are in this module?
This module has 6 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 grammar rule and reasoning behind it — 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 Grammar exercises?
Browse the full Grammar 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 grammar rules in prose; this exercise tests and reinforces those rules 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.