Developer Experience and DevRel

Decide what belongs in code comments, generated reference, and written guides so each reader can find the right kind of answer.

Most engineering documentation fails for the same reasons. Here is what actually moves the needle.

I analyze the structural correlation between documentation quality and engineering throughput, using DORA metrics and Accelerate research to quantify the ROI of technical writing.

I analyze the structural reasons why engineers filter for technical depth and verify-ability, creating a 5-tier hierarchy of developer trust.

I think Stripe’s technical blog compounds into a moat because it teaches, documents, and shapes developer trust long before a sales conversation starts.

DevTools startups lose deals long before sales hears the objection. I explain how weak docs break evaluation, trials, and rollout confidence.

I explain which engineering habits still make me better at technical writing, which ones I had to drop, and how the day-to-day work changed.

AI product docs now need prompts, schemas, evals, and version boundaries. I explain the rules I would use to judge a technical writer for an AI company.