Conditionals in IT Context
1st, 2nd, and 3rd conditionals used in bug reports, planning meetings, and architecture proposals.
If we merge this PR without tests, we'll introduce a regression. Grammar for IT English
Grammar taught through real IT sentences — not textbook examples. Every exercise uses vocabulary and scenarios you'll encounter at work.
12 topics
Passive Voice in Documentation
When and how to use passive constructions in technical writing, API docs, and incident reports.
The request is authenticated using a Bearer token. Modal Verbs for Recommendations
Should, could, must, might — choosing the right modal for code reviews, proposals, and risk communication.
You might want to consider caching this response. Tenses in Status Updates
Present perfect, simple past, and future tenses for sprint updates, post-mortems, and release notes.
We have deployed the fix. The service is now stable. Hedging Language
Express uncertainty, degrees of confidence, and cautious recommendations like a native English speaker.
This might be related to the memory leak we fixed last sprint. Transition Words & Cohesion
Connect ideas smoothly in technical writing: however, therefore, given that, as a result, in contrast.
The API is fast; however, it lacks proper error handling. Reported Speech in Meeting Mins
Accurately summarise what was said in meetings, standups, and design reviews.
The tech lead suggested that we refactor the auth module first. Quantifiers & Approximators
Several, numerous, a majority of, a handful of — precise quantifiers for metrics and scope discussions.
A significant portion of users are on mobile browsers. Relative Clauses in Tech Docs
Which, that, who, where — building clear technical descriptions for APIs, components, and processes.
The endpoint which handles authentication must be rate-limited. Noun Phrases & Technical Stacking
IT English uses dense noun phrases. Learn to read and write them clearly: "distributed event-driven microservice architecture".
We need a rate-limit-aware retry backoff strategy. Punctuation in Code Comments
Correct use of semicolons, colons, dashes, and parentheses in inline comments, changelogs, and docs.
// TODO: refactor this — the current approach is O(n²) Concise IT Writing (Cut the Filler)
Identify and remove redundant phrases, passive overuse, and vague language from technical writing.
In order to → To | Due to the fact that → Because