Not the first time I've read descriptions of this kind of behavior (let's call it social conformity) presented as perfectly normal, and I read comments (here and elsewhere) that largely confirm this is normal.
It's pathological dysfunction, however common it may be.
It seems to be adept at reviewing/editing/critiquing, at least for my use cases. It always has something valuable to contribute from that perspective, but has been comparatively useless otherwise (outside of moats like "exclusive access to things involving YouTube").
Most folks don't seem to think that far down the line, or they haven't caught on to the reality that the people who actually make decisions will make the obvious kind of decisions (ex: fire the humans, cut the pay, etc) that they already make.
If you've got a solution to the problem of bad decisions made by people who shouldn't be empowered to make them in the first place, you'll solve more than Claude Code.
Some people want the thing done more than they want to do the thing. That gets to extremes of exploitative parasitic behavior, but it's true at much less obnoxious scales: ever used a programming language's standard library instead of inventing your own _whatever_? Probably a yes.
That can extend to arbitrary absurdity. You are probably not growing your own food, mining your own ore, forging your own tools, etc etc etc.
It's all just a matter of where you rely on external tools/abstractions to do parts of the work you don't want to do yourself.
On my Windows machines, every time I have to click my Bluetooth icon, which is about a dozen times every day, the full second pause before it presents me with a menu makes me wish I didn't need Windows on two of my systems. It's mindbogglingly stupid that a UI element has a one second delay to present a menu on...any hardware, much less "2025" hardware.
But that's the kind of product they're shipping, because that's the kind of people they're employing, and that's the kind of decisions they're allowed to make. It permeates everything.
And on laptops you may need to write a script to disable Bluetooth before the lid closes and re-enable it when the lid opens because Microsoft in its wisdom forced S0 sleep but didn't care to make it stable enough so a drivers can't crash your system during it.
Additionally there is no reliable mechanism to do so as doing it through Task Scheduler causes a race condition - will your script be allowed to run and finish before S0 sleep cuts power to it? You can not be sure.
Additionally if you got cornered into making an online account Task Scheduler doesn't even work with that reliably (for task that require privileges like turning off BT on lock and turning it on on unlock) so then you have disable the online account Microsoft manipulated you to make. Of course the failure is silent so you have to discover all that by yourself.
That is a a driver but Windows can also crash during S0 sleep because of its own updater failing to update some random app (like Microsoft Phone w/e that is).
On Linux it's just not an issue. The script runs on events and is guaranteed to finish. Random updates at random times won't happen either.
In any event, I don't think you're going to get any kind of support from OpenAI by posting it here. They don't understand how any of it works either so they won't be able to tell you why you get "echoes" of previous answers.
It's pathological dysfunction, however common it may be.
I suppose you can't see it when you're in it.
reply