I've spent about twelve years in technical support and adjacent engineering, following a path from manufacturing IoT apps to CI/CD support, Vercel, and Cursor.

My working thesis is simple: support investigations are research problems. The slow part is rarely writing the response. It is gathering the right context from code, logs, tickets, and team conversations.

At Cursor, we collapse that work into one session using MCP, multi-root workspaces, rules, and parallel subagents. In our team write-up, the team reports that over 75% of support interactions run through Cursor, with a 5–10× increase in support-engineer throughput.

Away from the queue, I make functional 3D-printed things: useful fixes, adapters, holders, and the occasional oddly specific household part.

WORK / 01

Writing / technical support

“How technical support at Cursor uses Cursor”

Co-authored with Kody Fisher and published March 3, 2026. The team write-up covers starting from the codebase, bringing support context into Cursor, and running investigation work in parallel. It reports that over 75% of Cursor support interactions run through Cursor, increasing support-engineer throughput 5–10×.

Read at cursor.com

Vercel Community / @hud-code / Vercel Alum

ISR observability Bots + image caching