Technical editor. I check documentation against the code it describes, and technical reports against the sources they cite. → liamdgray.com
Most editing catches sentences that are unclear. The expensive errors are the ones that read perfectly and contradict the implementation — a documented status code the handler never returns, a parameter renamed two releases ago, a number that was plausible and invented. Finding those requires being able to open the repository.
That is what the ECE degree and the embedded years are for.
- Developer documentation — READMEs, integration guides, tutorials, checked against the code.
- API references — endpoints, parameters, status codes, and error shapes compared with the implementation.
- Technical reports — claims traced back to the sources supposed to support them.
- Documentation audits — what is missing, what is wrong, and what to fix first.
Every job ships two files: the corrected document, and a change log explaining each change — including the places I refused to invent a fact and asked a question instead.
I use AI for first passes. The judgment calls and the final text are mine.
Public work, mostly building the kind of systems whose documentation I would be editing:
| Repository | What it is |
|---|---|
| medplum-mcp | MCP server for HL7 FHIR healthcare systems — Python reference server and a Rust workspace. |
| modbus-mcp | MCP server for industrial Modbus devices, written in Rust. |
| procore-mcp | MCP server for the Procore construction API, written in Python. |
| realpeep-public | Public mirror of an anonymous proof-of-capture system using zero-knowledge hardware provenance. |
| TrackXY | Real-time tracking of a point in webcam video, originally built for a torsion pendulum experiment. |
| blog | Drafts and notes. |
The rest are forks of other people's projects, kept for reading.
- Carnegie Mellon University — B.S. Electrical & Computer Engineering, Research Honors.
- Embedded systems — device drivers, DMA engines, RTOS integration, hardware bring-up. Assembly-level debugging, where a wrong comment is a wrong system.
- Teaching — substitute and guest teacher across hundreds of classrooms, 2017 to present.
- Research — literature pipelines and graph-based evidence systems, documented and maintained.
Small, scoped editing engagements. Fixed price, quoted before work begins, one at a time.