5 exercises — choosing between will, going to, and present continuous for IT planning, releases, and technical decisions.
0 / 5 completed
1 / 5
A team member sends a message in the deploy channel: "Tonight, I _____ the hotfix to production at 22:00 UTC — the schedule is already confirmed." Which form is correct?
Option B is the most natural choice here. Present continuous (am deploying) is used for fixed future arrangements — events already in the diary with a specific time. A confirmed deploy slot at 22:00 UTC qualifies: the plan is firm and the time is set. "Will deploy" (Option A) expresses a decision or prediction, not a pre-arranged plan — it sounds like a spontaneous decision made in the moment. "Going to deploy" (Option C) expresses a firm intention based on a plan, but it lacks the sense of an existing, concrete arrangement. Present simple (Option D) is used for timetabled events (flights, official releases) — possible, but less natural for a team deploy. IT pattern: "The pipeline runs at midnight" (scheduled), "We're releasing on Friday" (arrangement).
2 / 5
An architect is leading a quarterly planning meeting. She says: "Our codebase is growing too fast. _____ to Kubernetes next quarter — we've already evaluated the options."
Option B is correct. "Going to" expresses a firm intention based on a prior decision or visible evidence. The phrase "we've already evaluated the options" is the key signal: the team has done groundwork and made up their mind. This is the classic "going to for plans" rule. Compare: "Will migrate" would sound like a spontaneous decision or a general prediction, not the result of deliberate planning. Present continuous (Option D) would also be acceptable if a schedule were set — "We're migrating in March" — but without a fixed date, "going to" is the better fit. Summary for IT: going to = "we've decided based on evidence / groundwork already done"; will = "I've just decided / I predict"; present continuous = "it's scheduled / in the calendar".
3 / 5
During a standup, a developer says: "The load tests look worrying. If we don't add caching, _____ performance issues in production."
Option A is correct. "Going to" is used for predictions based on visible evidence. Here the evidence is clear: the load tests are already showing warning signs. This is the "evidence-based prediction" use of going to. Compare: "Will have" (Option B) would work for a neutral prediction without specific evidence in sight — "adding caching will improve p99 latency" — but when you can point to current data, going to is stronger and more natural. Present continuous (Option C) would mean the performance issues are happening right now, not in the future. IT pattern: "The memory usage is climbing — we're going to hit the limit" (evidence visible now). "We will need to scale horizontally as traffic grows" (logical future prediction).
4 / 5
A product manager drafts a sprint kick-off note: "Sprint 42 _____ on Monday at 09:00. Please ensure your tickets are groomed before then."
Option C is most natural here. Present simple is used for scheduled, timetabled events — events that happen according to a programme, calendar, or recurring schedule. Sprint starts are planned in advance and follow a fixed cadence. "The sprint begins on Monday" feels the same as "The flight departs at 09:00" — a timetabled fact. Present continuous (Option B) is also acceptable and common ("The sprint is starting Monday"), suggesting a concrete arrangement. "Will begin" is less idiomatic here because it sounds like a prediction or an announcement, not a reference to the schedule. "Going to begin" would suggest a firm intention rather than a timetable event. IT examples: "The maintenance window closes at 06:00." / "The release ships on the 15th." / "CI runs every merge to main."
5 / 5
A senior engineer is discussing a long-term roadmap item: "We haven't decided exactly when, but at some point _____ the monolith into microservices."
Option C is the most appropriate. When the timing is uncertain and no specific arrangement or evidence is mentioned — just a general future intention or prediction — "will" is the neutral, unmarked future form. The key phrase is "haven't decided exactly when": this rules out both the present continuous (needs a fixed date) and "going to" (needs either a firm plan or visible evidence). Present continuous (Option A) implies a specific arrangement is in place, which the sentence explicitly denies. "Going to break" (Option B) implies a firmer, evidence-based intention — possible, but "will" is less committed and matches the vague timeframe better. IT pattern: "We will eventually move to a serverless architecture." / "This service will be deprecated in a future version." / "The team will grow as requirements increase."