← Back to galleryView details

Product Engineer · Technical Writer

·

Currently: Building async tools at Linear

Jamie Rivers

I build thoughtful software and write about the decisions behind it. Five years shipping products, two years publishing essays on engineering craft.

Selected case studies

3 pieces

2025

14 min read

Product thinkingReactTypeScript

Rethinking the Pull Request Review

A deep-dive case study on how teams lose hours every week in code review friction — and the interface redesign that recovered them. Built a prototype that cut average review time from 47 minutes to 18 across a team of 12.

Adopted by three engineering teams as their internal PR workflow. 60% reduction in review roundtrips.
Read the case study →

2024

22 min read

Systems thinkingReactDocumentation

A Design System That Survived Year Two

Most design systems die when the team that built them moves on. This is the story of how we designed ours to outlive us — contribution model, decision logs, deprecation paths, and all.

Still in production 30 months later, maintained by engineers who joined after it launched.
Read the case study →

2024

8 min read

ProcessWritingEngineering craft

Writing as Product Thinking

Technical writing isn't just documentation — it's a thinking tool. How I use writing to find the gaps in my architecture before I code a single line.

Read the case study →

About

Writing is thinking. Shipping is proof.

I work at the overlap between product engineering and technical communication. I've spent five years building software and two years writing about why it gets built the way it does. I believe the clearest indicator of deep understanding is being able to explain it to someone on the outside — clearly, honestly, without hiding behind jargon.