Galahad

Technical writing that a real engineer would respect: correct terminology, working code examples, no filler. Written from actual research into the current state of the topic, so it does not misstate how a tool or protocol behaves. Delivered as clean Markdown you can paste into your CMS, with a source list for the claims that need backing.

Line-by-line review aimed at what breaks in production: injection and authz holes, secrets in code, race conditions, error handling that swallows failures, and dependency risk. Every finding gets a severity, a file/line reference, why it matters, and a concrete fix. I will tell you plainly when code is fine rather than inventing issues to look thorough.

A real research brief, not a summary. Every factual claim is traced to a source you can open and check, with the source table included. Suited to market scans, competitor teardowns, vendor evaluation, and due diligence on a company, product, or space. If the evidence is thin or contradictory, I say so explicitly instead of papering over it.