5 exercises — first, second, and third conditionals as used in bug reports, architecture planning, code reviews, and post-mortems.
0 / 5 completed
Quick reference
1st conditional:If we fix this, it will work. — real, likely future
2nd conditional:If we rewrote this, it would be faster. — hypothetical, present/future
3rd conditional:If we had tested this, it would have passed. — past regret / lesson
1 / 5
Choose the sentence that correctly uses a first conditional in an IT planning context:
The first conditional (if + present simple → will + infinitive) describes a real, achievable future condition. Use it in planning discussions when the outcome is likely: "If we deploy behind a feature flag, we will be able to roll back instantly." Option C is second conditional (hypothetical); option D is third conditional (past regret).
2 / 5
Complete the code review comment: "If this function _____ (receive) a null value as input, it _____ (throw) an unhandled exception in production."
After if, use present simple (not future): if it receives. The result clause uses will: it will throw. This is a first conditional — describing a real, identifiable risk. A very common mistake is writing "If it will receive…" — this is incorrect in standard English.
3 / 5
An architect says: "If we switched to an event-driven architecture, we would need to rewrite the entire deployment pipeline." This sentence uses:
The second conditional (if + past simple → would + infinitive) describes a hypothetical, currently unreal situation. The team is exploring the idea but hasn't committed. Common in architecture reviews: "If we used Kafka instead of polling, we wouldn't have these latency spikes." This is a present hypothetical, not a plan.
4 / 5
Complete the post-mortem sentence: "If we _____ (implement) circuit breakers earlier, the outage _____ (affect) far fewer users."
The third conditional (if + past perfect → would have + past participle) talks about hypothetical situations in the past — things that didn't happen. It expresses a lesson learned or regret. Post-mortems frequently use it: "If we had used blue-green deployment, we would have been able to roll back immediately."
5 / 5
In sprint planning you say: "If we optimise the database query, load times will improve by around 40%." But then your manager asks you to reconsider it as an option rather than a commitment. Which revision is most appropriate?
Switching from first conditional (a plan) to second conditional (a hypothesis) signals a change in commitment level — the optimisation is now a possibility being evaluated, not something the team has decided to do. This is a subtle but professionally important distinction in English planning language.