Most of what it said about the facts was intelligible actually. But I still couldn’t understand the connection or its significance. We may be staring at the future of AI - a form of intelligence that is alien to us.
> Note: the potential for a console freeze was previously noted but ignored. handoff-4.3-done.html stated, "could not break console, but [will need fixed later if I'm wrong]."
One could imagine that a perfect writer might also append: "It could be worth looking into what caused that wrong assumption, to prevent similar cases in the future," at most.
Everything else seems to be bad attempts at relatable writing to invoke emotion (an exercise that we should really stop trying to train emotionless matrix weights to attempt).
One of the things actual science fiction got wrong: to the extent that the thing AI does can be called "understanding", emotion is not unusually difficult for them to understand.
The unsurprising part once it was clear that approach was viable, was that humans wouldn’t be able to help but anthropomorphize it. I feel like the movie Ex Machina is more relevant than ever.
"Dead drag handle" "Booked half day you don't get back"
It'll go in CLAUDE.md
One thing about it I really hate, and haven't seen a lot of people mentioning, is how it navigates multiple abstraction levels in a single sentence. E.g.
> Worth stating because four documents now assert it.
Meta commentary on the task?
> a dead drag handle
Drag handle seems to be referring to some UI element. What does it mean for it to be dead?
So far no big deal
> during a booked half-day you do not get back
Do you not get the drag handle back? Or the half day?
Was the drag handle dead during the booked period? (Now I assume this is a calendar UI) And why does it matter (for this sentence) if you get it back or not.
> handoff-4.3-done.html's own wording
Treats verbatim filenames as subjects
> 4.4's review page
Probably referring to a file? I'm guessing handoff-4.4-review.html? No cohesion. And now it's actually the object of the sentence?
> downside of being wrong is that half day
Wait what's the downside? Who's being wrong?
> Checked, not recalled.
Then it jumps back to a meta commentary on the methodology for asserting the above. Why does this belong to the text?
"I'm not a programmer or software engineer. Don't talk to me like I am. Avoid coder jargon and vernacular. Explain things to me in a clear way, emphasizing a conceptual view that even an inexperienced person can understand. If helpful, use analogies and examples to illustrate and help you communicate."
It just ignores it and spits out drivel that sounds exactly like what you're getting.
They need the prompt to encourage expert outputs but unfortunately we also get ‘pretending to be an expert’ outputs since there’s a large amount of polluted training data for this.
If I recall, previous attempts to do so made them get stuck in edit loops.
like imagine this being our future, I don't know what we're even doing anymore
I got one too many chunks of this nonsense and told Claude to knock it off, forever. It acknowledged and wrote out some instructions to its memory about it.
And what a breath of fresh air. Its responses are maybe 20% longer but I read them at least twice as fast. Should have done it a long time ago.
What does it do? It says "found the smoking gun! Ooops I wasn't meant to say that - I found the problem!"
https://github.com/tkgally/je-dict-1/blob/main/.claude/skill...
Fable wrote it specifically for this project.
Source: I'm half brain dead from decoding a lot of Claude speak from it directly and colleagues' new way of communicating with me.