What Topics Does Greg Tatum Write About in His Technical Writing?
Updated
Greg Tatum's technical writing focuses on taking technology apart to see how it works, with the site explicitly naming Unicode, browsers, machine translation, and graphics as example subjects. If you want writing that explains the internals of computing systems rather than product news or tutorials, his Technical Writing section is the place to start. The site describes this work as sitting alongside his creative work and engineering practice, so the writing tends to connect technical detail with the broader question of how computers bridge computation and culture.
The stated scope of the technical writing
The site's own description of the Technical Writing section is the clearest guide to its range:
"Taking technology apart to see how it works—from Unicode and browsers to machine translation and graphics."
That single line sets the boundaries:
- Unicode — text encoding and the systems that represent human language in software.
- Browsers — the platforms that render and run the web.
- Machine translation — how software handles translation between languages.
- Graphics — visual computation and rendering.
These are examples rather than an exhaustive list, but they share a common trait: each is a layer most people use without seeing, and each rewards a close look at its mechanics.
What kind of writing to expect
The framing "taking technology apart to see how it works" signals an explanatory, mechanism-first style. The goal is understanding how a system functions, not announcing a release or reviewing a product. That makes the writing relevant if you:
- Want to understand the internals of tools you already use.
- Are interested in the overlap between language, visual media, and computation.
- Prefer explanations that start from how something works rather than what it does.
Because the site pairs this with creative work and engineering, the technical writing is one part of a larger practice rather than a standalone blog about a single product.
How to read it
The Technical Writing section has its own entry point on the site, listed alongside Creative Work. From there you can browse the articles directly. The site also offers an RSS feed, which is the practical way to follow new writing without checking back manually.
Where it fits
The site's overall description—"I explore how computers bridge computation and culture through writing, art, and engineering"—explains why these topics appear together. Unicode and machine translation are as much about language and culture as about code; browsers and graphics are as much about visual media as about engineering. If your interest is in that intersection, the technical writing is likely to be relevant. If you are looking for framework-specific tutorials or product comparisons, the stated scope suggests you will need to look elsewhere.