Tag: Claude

The most productive engineers I work with spend more time in conversation than in their editor. They describe, review, and decide — and the code appears as a side effect. This isn't laziness. It's the new craft. Here's what I'm seeing.

We used to measure engineering output in pull requests. That metric is about to break in ways that matter. The real artifact of work is shifting upstream — to the prompt, the spec, the intent. Here's what that means for how we work, review, and hire.

Last quarter I shipped more working software than the entire year before it. Not because I worked harder. Because I finally admitted the bottleneck was never my typing speed — it was everything else.

The most valuable thing Claude gave me isn't better code. It's the removal of the psychological friction that kills most projects before they start. When you have a judgment-free thinking partner available at 2am, you ship things you'd have talked yourself out of.