Claude has a place for simple tasks. It does a great job of being an “advanced find in files” or being a “smart boilerplate generators” but anything remotely more complex and the issues start to show, really quickly. When writing new prototype code, it does very well. But when you have to handle all sorts of edge cases, it doesn’t do it as well. It also doesn’t do a good job with debugging anything more than surface level. Opus does slightly better, but even then gets into the frequent “I found the issue! oh wait, that’s fine. I found the issue! Oh wait, that’s fine” loop over and over again.

And before you ask: Yes, I’ve been using Copilot CLI for work pretty regularly for the past couple months.

Aside: It doesn’t help that the true token costs are off by a factor of 100-1000. Yes, I know general reporting is saying the breakeven is 10x, but…well, you’ll have to trust me that’s not accurate.

“Wait, why is this not a CSV file?”

One (contrived) example would be to have a drive that doesn’t have any installed file system filters on it. Filters being the hooks that windows, antivirus, etc have that intercept file writes and such. Could make it much faster on windows for that use-case. I can see custom software using that drive.

Contrived? Definitely. But potentially useful. I can see it working similarly to something MS has in testing which is the file system thing that is super fast but is limited in features—can’t seem to find it atm…

Edit: Found it. Dev drive via ReFS.