In our latest developer productivity survey, our documentation was the area with the second most comments. This is a writeup of the concrete steps I took to see how much progress one person could make

While Staff Engineer was first and foremost an attempt to pull the industry towards my perspective on staff-plus engineering roles, writing it also changed my opinions in a number of ways. Foremost, i

Remotion is having a bit of a moment at the moment, and I decided to play around with the Claude Code integration. Here are a couple videos I was able to make in <10 minutes summarizring data on my bl

Despite my best efforts, I have been wrong a lot over the years. I’ve been wrong about technology patterns (in 2014, I thought microservices would take over the world), I’ve been wrong about managemen

I did a lot of hiring at Uber, some days I would be doing back-to-back 30 minute phone screens for several hours in a row. That said, while Uber taught me how to hire at scale, it was Stripe that taug

When we launched Digg v4, the old site turned off, but the new site didn’t turn on. There was a lot of pressure to get things working, but no one knew what to do about it. It took almost a month to ge

Every's compound engineering breaks down AI coding into 4 patterns: planning (decoupling research from implementation) and executing work.

Team built internal system to share Claude Code transcripts, making it easier for colleagues to discover effective LLM prompting examples.

Author switched newsletter from Mailchimp to Buttondown after 6 years due to mounting frustrations with Mailchimp's interface and usability issues.

Imprint is documenting lessons learned while building internal AI agent workflows, covering topics like prompt libraries, evals, logging, and workflow design.

Companies must iteratively refine AI agents to build employee intuition for automation, developing talent in-house rather than acquiring it externally.