There could not possibly be a single thing in the world more boring than listening to someone describe using an AI agent. Might as well describe in arduous detail how you use a gas pump or a grocery store checkout.
I'm very much on the side of "artisanally writing all code by hand" in terms of preference, but I have to admit that sometimes it puts me in a bind where there's stuff I wish I could do but don't because it's too time-consuming for the value provided. Isolating repro cases sometimes falls into that bucket.
This seems like a good use case for AI. Even if the resulting code isn't great, as long as it repros the issue and is fairly small, it's fine. It's eventually throwaway code anyway. At best, it will be harvested for a test case, but otherwise it's gone once the bug is fixed.
I might be too used to using coding agents in various parts of my workflow, and others are still getting acquainted, or others find it still much different than just another standard debugging tool.
And fwiw it's probably not Claude's fault that emoji fonts load this slow, though. Wtf Safari?
There are plenty of people learning to use AI and this article helps them.
A reasonable amount of repetition of "things you should know" is good.
The article is well written because you could skip the parts you knew, and learn from the parts you were unfamiliar with.
The article explains using AI beneficially for a professional task.
TL;DR: It will pass as AI agents become more boring (a good thing) and there's a standard workflow.