We're trying to make billions of dollars here, we don't have time to do crazy things like test basic functionality before shipping changes to all live users at once

Ironically that might have passed, because this didn't break the version, this broke all versions when the global referenced changelog was published. It wasn't the new version itself that was broken.

But testing new version would have been downloading the not-yet-updated working changelog.

There are ways to deal with this of course, and I'm not defending the very vibey way that claude-code is itself developed.

I just set this up for the project I'm working on last week, and felt dirty because it took me a couple of months to get to it. There are like 5 or 6 users.

There's something so unnerving about the people pushing the AI frontier being sloppy about testing. I know, it's just a CLI wrapped around the AI itself, but it suggests to me that the culture around testing there isn't as tight and thorough as I'd like it to be.

The irony is that I have a Claude agent to do exactly this on my projects. You’d think they would have thought of that too.

Considering how shitty tests my coworkers are producing with Claude, I'm not all that surprised.