JWJunhe Wang

AI · DATA · ROBOTICS · DEVELOPER TOOLS

Technical content that runs before it claims.

I reproduce the workflow, capture the exact command and boundary, then write the tutorial, evaluation note, or engineering case study. Async delivery only—no meetings required.

  1. 01Every command is checked against the shipped version or official documentation.
  2. 02Vendor claims are attributed; observed results are kept separate.
  3. 03Secrets, customer data, and unsupported performance claims stay out.
  4. 04You receive editable Markdown plus a verification log.

WHAT I CAN DELIVER

Small, verifiable assets your engineering audience can actually use.

Product tutorial

A task-led walkthrough for a CLI, API, SDK, agent, data tool, or evaluation workflow.

  • Runnable path
  • Prerequisites and safety
  • Official-source links

Engineering case study

A credible story built around the real constraint, intervention, evidence, and boundary.

  • Technical narrative
  • Result interpretation
  • No invented metrics

Evaluation note

A concise report comparing tools, model behavior, or workflows under explicit conditions.

  • Test matrix
  • Failure cases
  • Decision-ready summary

RUNNABLE SAMPLE

Interactive autonomous-driving long-tail audit in marimo.

FIXED-SCOPE PRICING

Start with one useful artifact. Expand only after it works.

Technical accuracy audit

$99 fixed

Review one draft up to 1,500 words. Check commands, links, unsupported claims, and reader-blocking gaps.

  • Annotated Markdown
  • Claim and command log
  • One revision pass

Content sprint

$699 fixed

Three coordinated assets around one product or engineering theme, delivered asynchronously.

  • Three scoped drafts
  • Shared fact ledger
  • Consistent terminology

SELF-SERVICE OPTION

Prefer to run the review yourself?

ASYNC WORKFLOW

No discovery call. A written brief is enough.

Brief

Audience, product, desired action, approved sources, and confidentiality boundary.

Reproduce

I verify the smallest useful workflow and record exact versions and commands.

Draft

I write around observed behavior, official sources, and explicit limitations.

Deliver

You receive editable Markdown, assets, and the verification log.

BOUNDARIES

Good technical content is precise about what it did not prove.

Included

Public or client-approved material, local reproduction, source checking, diagrams made from non-confidential facts, and one agreed revision pass.

Not included

Fabricated benchmarks, copied customer material, fake user stories, academic ghostwriting, credential handling, or unreviewed production access.

Best fit

AI infrastructure, data engineering, robotics, evaluation, developer tooling, technical recruiting, and research-facing products.

Send a written brief, not a meeting invite.

Use the template to specify the audience, deliverable, approved sources, deadline, and anything that must remain private.