Skip to content
View LiamDGray's full-sized avatar

Block or report LiamDGray

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
LiamDGray/README.md

Liam D. Gray

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.


What I do

  • 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.

A worked sample →

I use AI for first passes. The judgment calls and the final text are mine.


What is here

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.


Background

  • 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.

Working together

Small, scoped editing engagements. Fixed price, quoted before work begins, one at a time.

Website • Editing sample • Contact

Pinned Loading

  1. TrackXY TrackXY Public

    Track position of a point in webcam, in realtime, based on OpenCV's Lukas-Kanade demo code. Originally designed to enable a torsion pendulum experiment. Original build is Windows console app using …

    JavaScript

  2. medplum-mcp medplum-mcp Public

    High-Assurance Model Context Protocol (MCP 2.3+) Server for HL7 FHIR Healthcare Systems

    Rust

  3. modbus-mcp modbus-mcp Public

    Rust

  4. realpeep-public realpeep-public Public

    Public mirror of my work in progress: anonymous proof-of-capture — ZK hardware provenance, acoustic co-location, duress-safe receipts, offline verification. Apache-2.0.

    Python

  5. procore-mcp procore-mcp Public

    Python