An original benchmark of 200 requests across 7 targets, comparing performance and cost for large-scale scraping.
Editorial choice. I showed the method before the verdict so readers could assess the result.
Read articleTechnical writer for AI and developer tool companies.
I trace technical ideas to the source, shape them into clear content, and help that work reach developers through organic distribution.
Written for
Actian · Bright Data · Zenrows · ToolJet
Services
Technical content backed by research and hands-on testing.
I help AI and developer tool companies create technical content and distribute it where developers already spend time.
Technical Articles
Explainers, architecture guides, benchmarks, and industry analysis written for technical readers.
Learn more Developer TutorialsTested API, SDK, and integration guides that take developers from setup to a working result.
Learn more Product-Led ContentUse cases, comparisons, and workflow guides that show where a product fits and how developers can use it.
Learn more Technical Thought LeadershipResearch-backed articles that turn experience, data, or a technical position into a clear argument.
Learn more Technical Content DistributionOrganic distribution across developer communities and social platforms to help published content reach the right readers.
Learn more
Selected work
Read the work and judge for yourself.
My portfolio includes original benchmarks, developer tutorials, AI architecture guides, and analysis published by technical companies and developer publications.
A tutorial for building a stateful research agent with LangGraph, retry logic, and live web scraping.
Tutorial goal. I built the tutorial around a complete path from setup to a working agent.
Read articleA step-by-step guide to swapping smolagents' default web tool for a Zenrows-powered one so AI agents can read JavaScript-rendered and bot-protected pages.
Problem I solved. I focused on the production gaps left by the default web tool.
Read articleAn architecture guide for running AI at the edge with no cloud connection required.
What pulled me in. Different industries were solving the same offline AI problem without shared language.
Read article
How I think
I follow the argument until it holds.
Mathematics trained me to question conclusions that skip steps. I read the documentation, test the product, find the central argument, and build the story around it.
Technical depth
I read the documentation, test the product, review the source material, and speak with subject-matter experts when the project calls for it.
Technical judgment
My background in mathematics and machine learning helps me question weak claims, follow technical reasoning, and find the part readers need explained.
Structure
I give each piece a clear argument and build the explanation around what the reader needs to understand or do.
Case studies
See how I approach the brief.
Each case study covers the research, editorial decisions, finished work, and results behind a published project.
Case study
A Reproducible Benchmark for Large-Scale Web Scraping
Challenge. The piece needed a fair test methodology, several protected targets, and transparent reporting across performance and cost.
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 PatternsChallenge. The relevant patterns were spread across separate industries and rarely named or compared. The article needed to connect those examples to the decisions an architect makes when cloud connectivity is unavailable.
Approach. Researched how inference and control run offline across those industries, then organized the findings into five patterns. Each pattern explains its constraints, trade-offs, and suitable environments.
Outcome. Published on Actian's developer blog, where it ranks number one in search for the "edge AI architecture" keyword.
View case study Case study Turning Vector Database Market Shifts Into an Architecture Decision FrameworkChallenge. The topic covered several connected shifts, including database consolidation, agent-driven query volume, infrastructure costs, and the limited support for edge deployments. The article needed to connect these developments without becoming a news roundup or a list of vendor claims.
Approach. Researched market acquisitions, database benchmarks, pricing models, deployment constraints, and emerging workload patterns. Organized the findings around three market forces, compared purpose-built vector databases with PostgreSQL and pgvector, and created a decision framework based on scale, performance, cost, and deployment requirements.
Outcome. The article ranks on Google's first page for "vector database news 2026," and Claude is its second-highest traffic source.
View case study
Process
How I work
Understand
We agree on the reader, the goal, and the role the content needs to play.
Research
I read the documentation, test the product, speak with subject-matter experts, and verify the claims.
Structure
I define the central argument and build an outline that supports it.
Write
The draft gives readers the context, explanation, and evidence they need.
Refine
I review the piece for accuracy, logic, repetition, and unnecessary language.
About
I trace ideas back to the source.
My background in mathematics taught me to follow an argument until every step holds. That habit now shapes how I write about AI, machine learning, developer tools, and the systems built around them.
Insights
Notes from the work of writing technical content.
Frameworks and editorial lessons from Tech & Storytelling.
Craft
The Hierarchy of Technical Content
A model for ranking technical content by how much work it does for the reader.
Read Craft Bridging Product and People in Technical WritingWriting that serves the product and the person using it at the same time.
Read Frameworks The PTS Framework: Problem, Tension, SolutionA structure for technical pieces that keeps a reader moving through the argument.
Read
Newsletter
Subscribe →
Technical writing lessons from published work.
A newsletter for technical writers who want to become better storytellers.