Just today I had my agent diff two logs to find a very nitpicky difference that was the cause of a problem, I pointed it at a ADO extension that was having issues, it downloaded the VSIX and decompiled the .NET binary to verify. Based on that information it suggested a workaround which I was very skeptical of, but well it worked.

All of this I technically could have done but I probably wouldn't because it would have taken too long without a clear payoff.

I think they make a great "second device" where you have something meatier to fall back to if something doesn't quite work right. I'm not sure if it's ready to take on the "main device" role just yet. But it's a far far better experience than the Surface RT days.

I run into this with AI-generated PR comments. I think where I work we are still grappling with the "right point", because LLMs can certainly provide valuable feedback, but they are not at the point where they can do so unsupervised, and to do so just feels unprofessional.

And there's another layer where it is even worse when a colleague spends the time critiquing code and someone (or something) replies to the comment with mostly useless filler. It's like being handed a small hand-crafted gift and then throwing it into the garbage in front of them.

Thinking more on this I think a business opportunity in the future will be companies that design hardware stacks that can go in random appliances that can gather usage information in the name of telemetry.

I give it +/- 5 years before an OTS coffee maker at walmart phones home.

I see a parallel here where a competitor's product is taking over and MS leaders see it becoming an existential problem and are putting their foot down and pushing internal users to the company's products.

Also if half the company don't even want to use something made by the other half it's a bad look lol

It's the same reason Teams got so much attention during lockdown.

This is your second paragraph but reads awkwardly. You mention two halves in the previous paragraph, so I kind of try to map those two halves to the halves in this paragrpah. But I don't understand what the second half is in this second paragraph.

> Three months ago the lodge's social channels went dark. Not for lack of content; the lodge has years of raw footage across multiple SSDs. The bottleneck was editing time, and my time disappeared. Claude Code with Opus 4.5 (and then 4.6) hit the point in February where you could leave agents running for hours and come back to merged PRs. KaribuKit was going live with its first paying property in the same window. I stopped sleeping properly, started running three or four agents in parallel in the background, and the months when I would have cut reels turned into months when I shipped software instead.

I don't fully understand this paragraph either. Your time disappeared? Into what? Was it the lack of sleep? I don't know what KaribuKit is.

> I asked it out loud: how does the agent know what's in each clip?

Did you? Really?

> Four bugs, four lessons

I've noticed that AI tends to rathole into random things when summarizing a piece of work, so I'm skeptical that these were actually the most four interesting bugs you could have shared.

I would recommend you just remove this section or take the time to actually think about some learnings you had from this project. Syntax errors or missed CLI params are mildly interesting but what makes these four bugs interesting to your readers?

> The actual take

The same criticism here applies. Are these your real takes, or did Claude make these up too?

Some obvious tells to me of things that AI likes to write that humans rarely ever say:

> Both real, both consuming attention.

> Four constraints set the shape:

There's way more than just this (the writing style of nearly the entire post screams Opus 4.7), but that's just what jumped out at me when I started reading your post.

I don't mind you used AI to write this but in the future when you write using AI, take the time to read the entirety of the article and consider the goals of what you want to write and if the AI achieved that. Take out what doesn't belong and make sure that what you have left says things in your voice.

I'm guessing though that there are other improvements in code quality and feature velocity. I've noticed personally that AI is really good at catching smaller things that are easy to miss (e.g., if you ask it to rename fooTheBars it also updates all the relevant comments or enums that you might have missed).

Robots have landed on Mars. Maybe they will even figure out how to use minerals on Mars to build more of themselves. It is plausible to me that as far as space exploration is concerned that it will be autonomous within a few hundred years.

You might not have merge conflicts but I imagine you could end up with conflicting guidance from two separate pieces of law (e.g., law A says you must wear green on St. Patrick's day, law B outlaws green pajamas).