Conjunctions in Technical Writing

Although is a subordinating conjunction that introduces a dependent clause with a full subject + verb structure (the latency was higher). Despite is a preposition and must be followed by a noun phrase or gerund, not a clause — e.g., despite the higher latency or despite latency being higher. However and Nevertheless are adverbs, not conjunctions; they cannot join clauses and require a semicolon or new sentence. IT examples: "Although the patch reduced memory usage, response times increased." / "Although the API is deprecated, it remains in use by legacy clients."

However signals contrast — the second sentence contradicts or qualifies the first. Therefore, Consequently, and Furthermore all imply a logical consequence or addition, which is the opposite of what is needed here. In technical writing, "however" is the standard adverbial connector for contrast between two related but opposing facts. Placement note: as a sentence adverb, "however" is followed by a comma. It can also appear mid-sentence with commas: "Peak-hour times, however, remain above the SLA threshold." Do not confuse with "although", which joins clauses within one sentence.

Whereas is the preferred choice in formal technical documents such as ADRs, RFCs, and design specs because it is explicitly contrastive and carries no temporal ambiguity. While is grammatically acceptable but can be read as temporal ("at the same time"), which may introduce ambiguity in architectural prose. But and yet are coordinating conjunctions suitable for informal writing but considered too colloquial for ADRs and formal specs. Rule of thumb: in technical comparisons, prefer whereas when the contrast is the primary message. Example: "The REST endpoint returns XML, whereas the GraphQL endpoint returns JSON."

", and" is correct here because it joins two independent clauses that are both positive outcomes and logically related — the second clause adds information rather than contrasting it. "The failover completed successfully, and data loss was minimal." ", however" placed after the subject of the second clause would require the structure: "The failover completed successfully; data loss, however, was minimal." — but that changes the meaning to imply contrast. ", therefore" would imply the second event caused the first, which is reversed logic. Postmortem writing tip: use and for parallel positive findings; use however for unexpected negatives after a positive.

Nevertheless is the most formal option and the standard choice in RFCs, technical proposals, and engineering specs. It concedes the preceding point while introducing a counterpoint. Even so and Nonetheless (not listed) are near-synonyms but slightly less formal. Still is grammatically valid but more common in spoken English and informal writing. Anyway is informal and dismissive — never appropriate in risk analysis. Formal register ladder (most → least formal): Nevertheless > Nonetheless > Even so > Still. In IETF-style RFCs and Google Design Docs, "nevertheless" or "nonetheless" are the accepted conventions for acknowledging risks after mitigation.