Technology journalism explains computing to people outside the lab: what a system does, how it works, who it affects and what is still unknown. The craft is verification and clarity. A good technical reporter understands the subject well enough to ask sharp questions and to tell a claim from a demonstration.
Key concepts
- Verification: check claims against primary sources, documents, code and independent experts.
- Sourcing: know who said it, how they know it and what they stand to gain.
- Explaining without distorting: simple language that keeps the caveats that matter.
- Reproducibility: where possible, run the thing yourself and report what happened.
- Corrections: publishing errors openly and fixing them quickly builds trust.
Vocabulary
- Primary source: the original paper, dataset, specification or filing, not a report about it.
- Attribution: saying where a fact comes from.
- On and off the record: whether a source's words can be quoted and credited.
- Benchmark: a measurement; its value depends on what was measured and how.
What to study, in order
- Take a news claim about a technology and trace it back to its primary source.
- Rewrite a technical paper's abstract for a general reader without losing its limits.
- Run a published benchmark or tutorial yourself and compare your results with the claims.
- Learn to read a specification or a changelog for what it really says.
- Study how published corrections are written, and write one for an error of your own.