Like a cold. Sometimes people call an illness a condition. A condition that can happen to you.

We have frameworks essentially living in a completely synchronous world--like a 2D plane--and they can't tell that there is another dimension out there except for when something inserts itself into its view out of nowhere. The protocol that we arrive at to deal with async is convoluted, because it is a state that is basically inflicted on the framework. That's what we sought to remedy.

Ah. The medical meaning, for an analogy. I think 99% of readers will, like me, take the software meaning. I'm sure Claude would know that if left to its own knowledge base, so I presume it was prompted to go way outside its training, hence the wierd word salad.

The article reads eerily like the Claude-authored drafts I did for some internal explanations of Relay’s design philosophy (it’s a GraphQL client I’ve been advocating for). I’m not one to make accusations of AI authorship, but it was a particularly striking impression with this one.

I had to rewrite the drafts very heavily in my own voice in order for people to enjoy reading them —- not that I’m a great writer, but I am human and people tend to appreciate that.

Hey want to see what AI generates when I ask it to talk about Solid 2.0. It's not that. It is:

https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/rJM9ws3Kbg https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/H1Q8XTMSbe

I probably wasn’t clear with my experience. I was trying to get Claude to present my ideas, with a lot of steering and refinement, but it always seemed to be plagued by Claudisms. Even after getting rid of most, it took me rewriting all the prose to get something which people felt comfortable reading.

The published post reminded my of where I got to after several rounds of review and cleanup.