Technical Content Built From Real Implementation Work

I'm an engineer who writes about engineering. I build production reference implementations of developer products and publish written assessments grounded in what actually works — the kind of technical content senior engineers trust because it can be cloned, run, and inspected.

A small number of durable assets. Built once, paying back across sales conversations, evaluation calls, and developer onboarding for years.

Independent technical publishing
15+ years production engineering
Ex-Apollo GraphQL
Official Render reference implementations

Why Independent Validation Matters

Your internal team saying your product is great is expected. An independent engineer saying it — after actually building with it — is proof. That's not an opinion; it's what 3,500 B2B buyers told Edelman and LinkedIn.

73%

of decision-makers trust thought leadership over marketing materials when evaluating vendors

Edelman-LinkedIn, 2024 →
75%

of decision-makers say thought leadership prompted them to research products they hadn't considered

Edelman-LinkedIn, 2024 →
66–72%

of B2B buyers trust independent experts — compared to just 58% for vendor salespeople

Forrester, 2025 →

How This Works

1

Evaluate

I use your product the way a senior engineer evaluating it for production would — real project, real constraints, honest findings. No sandbox demos. No content plan disconnected from what actually matters to developers and buyers.

2

Build

I turn that work into a focused content package: reference implementation, written analysis, and supporting assets that help a founder sell the vision with evidence.

3

Publish

The finished package is designed to keep paying back through trust, technical clarity, and reusable proof long after launch.

Blog

Field Notes

Read all posts →

If you run a developer tools company with a strong product and thin third-party proof in the market, I can help you scope the right package and keep it focused on adoption and pipeline — not output volume.