Why Tech Writers Should Always Define Their Jargon

A software developer argues that technical writers routinely assume readers understand domain-specific terms, creating barriers for beginners. Using the example of 'MV3' — Google's Manifest Version 3 — the author illustrates how an undefined acronym can confuse newcomers even in a beginner-friendly article. The post also challenges the common advice to 'just Google it,' noting that search engines personalize results, meaning different users may get entirely unrelated content for the same query. The author proposes a simple, low-friction solution: add footnotes to define acronyms and jargon, which experts can skip while novices benefit greatly. The core message is that authors control their article's context but not their readers', making clear definitions a small but meaningful act of inclusivity.