Technical content for AI and developer-focused companies.

I turn complex technologies into clear, technically grounded content that helps developers understand products, solve problems, and make better technical decisions.

Technical writer · AI/ML · Developer tools · Technical storytelling

Praise James, technical writer for AI and developer-focused companies

Written for

Actian · Bright Data · Zenrows · ToolJet

Why Praise

Technical enough to understand it. Writer enough to make people care.

Technical depth

Real time spent understanding the subject before writing a word: reading the docs, running the code, talking to the engineers. Not a generalist summarizing.

Storytelling

Content structured so readers can follow the argument and act on it. A clear thread from problem to solution, not a wall of correct information.

Reader-first

Written for the person who has to use the content (integrate the API, make the call, ship the thing), not the person who assigned it.

Case studies

How the work gets done.

The brief, the technical challenge, the approach, and what happened next.

Case study What Senior Technical Writers Know About Cross-Functional Impact Independent community research project

Challenge. The value of the role is often spread across product decisions, support, engineering, and internal communication, which makes it difficult to describe with a single metric or job description.

Approach. Interviewed nine senior technical writers, including practitioners from companies such as Google and Mastercard. Coded the interviews for recurring themes and used those themes to build the final narrative.

Outcome. The resource sparked sustained discussion among senior practitioners on LinkedIn, reached around 700 technical writers, and shifted how several of them framed the value of the role inside their own organizations.

View case study
Case study A Reproducible Benchmark for Large-Scale Web Scraping Zenrows

Challenge. Comparisons in this space are usually vague or self-serving. The piece had to define a fair methodology, run it across several real targets, and report results honestly, including where the product was not the fastest option.

Approach. Ran a defined test of 200 requests across 7 target sites, compared the platforms on performance and cost, and documented the method so a reader could reproduce it.

Outcome. Published as Zenrows' reference comparison for large-scale scraping, and ranks in search for "Apify vs Zenrows" and related evaluation queries.

View case study
Case study Turning a Fragmented Topic Into Five Usable Architecture Patterns Actian

Challenge. Edge AI for disconnected environments is real but fragmented: the patterns are spread across separate industries and rarely named or compared. The piece had to make the space concrete without a cloud fallback to lean on, and stay useful to an architect rather than drifting into abstraction.

Approach. Researched how inference and control actually run offline across those industries, then distilled the field into five distinct patterns (the Drone, the Factory, Hierarchical Federated Learning, Store-and-Forward, and the Network), each with its constraints, trade-offs, and the situations it fits.

Outcome. Published on Actian's developer blog, where it ranks number one in search for the "edge AI architecture" keyword.

View case study

All case studies

Process

Understand, research, structure, write, refine.

A practical sequence that keeps the content accurate and the timeline predictable.

Understand

Learn what you are building and who it is for. The content can only be as clear as the understanding behind it.

Research

Read the docs, run the product, talk to your engineers. Claims get checked so you are not defending the piece later.

Structure

Decide the one thing the reader should walk away with, then build the outline around that. Structure is where a piece is won or lost.

Write

Draft for the reader who has to act on it. Plain sentences, complete code, no filler between the reader and the point.

Refine

Edit for accuracy, flow, and length. Every round removes friction between your product and the person evaluating it.

About

I write about technology for a living.

I came into technical writing from writing, and into AI and developer tools from a background in mathematics and hands-on machine learning. Long enough in to know the hardest part is not understanding the technology. It is knowing what your reader actually needs to walk away with.

More about how I work

Newsletter

I write about making technical content easier to understand.

A newsletter for technical writers who want to become better storytellers.

Subscribe →

Need technical content for your AI product?

Let's work together →