Read Trust, and Reviewing Changes

Trust, and Reviewing Changes

6 min read

This morning on the drive back from school drop-off my Eleven Reader’s AI voice confidently proclaimed over my car stereo: Our team members still review…

Read Qwen Flash Preview is exciting

Qwen Flash Preview is exciting

3 min read

I’m lucky enough to have an M5 Max MacBook with 128gb of Ram, and I’ve been spending a lot of sweat this summer trying to…

Read Giving command-tab a break

Giving command-tab a break

1 min read

The other day while waiting for Claude to process prompts, I watched this video: (I know, the irony isn’t lost on me) It highlights the…

murphitup @murphitup · Jun 10

I want to trust AI with code enough that I’m no longer doing line-by-line reviews. But when I look at the code, even from frontier models, I’m still finding small things that feel smelly.

In a simple PR Sonnet 4.6 made, I just found it changing the default mock data constructor for all existing test cases away from the common case to a less-common scenario. All the existing tests passed because they asserted on things that weren’t changed. The update was technically sound, but it’s the kind of change that would feel weird to a human if they came across it later.

Read Jetbrains ????

Jetbrains ????

1 min read

In my new role as lead of the Android team for Day One at Automattic, I moved from writing ReScript in Visual Studio Code most…